We are probably saying the same thing - the option that IMO is not
good is requiring registration to read the repository and get the
artifacts. If registration happens when installing, or delayed until
first use of what was installed depends on the use case - both are
valid, and there are probably cases where one or the other type of
registration is not possible (for instance installing a "ready to run"
zip where registration should be performed on first use vs. installing
a headless app where registration on first use is not possible).
Henrik Lindberg
[email protected]
On Dec 2, 2010, at 10:43 PM, Thomas Hallgren wrote:
Shouldn't registration happen when you install? Many installers that
I've been using has this as a final step. You can be fairly certain
that you're on-line when installing and it's likely that you have
some kind of UI (or at least a shell), but perhaps that doesn't
apply when you run it the first time. I'm thinking headless products
meant to be run as part of a build, or things running as a service,
etc.
- thomas
On 2010-12-02 21:39, Henrik Lindberg wrote:
I would go with the "when being run" option as that makes it
possible to get each actual install as opposed to one registration
for someone that aggregates and redistributes...
- henrik
2 dec 2010 kl. 21:05 skrev Ian Skerrett <[email protected]>:
They are looking for sales leads.
There seems to be two options: 1) have them register beforehand
and then use https or 2) register the user thru a locking
mechanism when the code is run.
Any other options I might be missing
On 12/2/2010 2:47 PM, Pascal Rapicault wrote:
p2 does not have such support.
What are they trying to achieve with by having their user
registered?
- Protection so other can't install it?
- Sales lead?
- ?
Until now most of the solution I have seen involve registering
the user when the code is run.
On 2010-12-02, at 2:39 PM, Ian Skerrett wrote:
I am working with some people who want to promote commercial
products using the Marketplace Client. One thing they would
like to do is require a user to register for the product before
installing. Is this possible with p2 and can anyone point me
to documentation or examples.
btw, I have seen people use the basic https username/password
but I am looking for something that is more a standard
registration page for new users.
Thanks
Ian
--
Ian Skerrett
Director of Marketing
Eclipse Foundation
Tel: 613-224-9461 ext 227
Blog: ianskerrett.wordpress.com
Twitter: IanSkerrett
Save the dates for EclipseCon 2011, March 21-24
www.eclipsecon.org
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
--
Ian Skerrett
Director of Marketing
Eclipse Foundation
Tel: 613-224-9461 ext 227
Blog: ianskerrett.wordpress.com
Twitter: IanSkerrett
Save the dates for EclipseCon 2011, March 21-24
www.eclipsecon.org
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
