View previous topic :: View next topic |
Author |
Message |
codenut
Joined: 13 Apr 2005 Posts: 12 Location: Ontario Canade
|
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Fri Apr 14, 2006 11:35 pm Post subject: |
|
|
You don't have to license the individual modules completely independently (ie a separate license key for each module). Instead you can embed the information about the licenced modules in the license key ProductInfo. That way you can issue a single license key and then read the ProductInfo to see which modules should be enabled. Depending on how you issue license keys you may want to create a CustomGenerator plugin for LicenseTracker that provides a user interface to make issuing keys easy. _________________ Infralution Support |
|
Back to top |
|
|
codenut
Joined: 13 Apr 2005 Posts: 12 Location: Ontario Canade
|
Posted: Fri Apr 14, 2006 11:47 pm Post subject: |
|
|
Infralution wrote: | You don't have to license the individual modules completely independently (ie a separate license key for each module). Instead you can embed the information about the licenced modules in the license key ProductInfo. That way you can issue a single license key and then read the ProductInfo to see which modules should be enabled. Depending on how you issue license keys you may want to create a CustomGenerator plugin for LicenseTracker that provides a user interface to make issuing keys easy. |
is there any chance you could give some guidance (code example) of how this would be done - not sure I follow 100% _________________ Steven
WinExtra
http://www.winextra.com
news://news.winextra.com |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Sat Apr 15, 2006 12:05 am Post subject: |
|
|
Simply assign each module a one digit identifier eg
A = Basic Module
B = Advanced Module
C = Integration Module
For admin purposes I don't think you'd want any more than 10 anyway. Then your product info can simply be the list of purchased modules ie "AC" means they've purchased Basic Module + Integration Module. Because you don't want to have to remember this mapping you would create a custom user interface that just allows you to tick the appropriate check boxes and generates the ProductInfo for you - see the CustomGenerator sample project for an example.
The disadvantage is that if your payment/license issuing system is fully automated it is more difficult to manage cases where customers want to add extra modules (without paying for ones they have already purchased). If you manually issue licenses this is not a problem because you can simply issue a new license which includes their previous licensed modules plus new ones they have purchased.
For fully automated license issuing it is probably easier for you to issue separate licenses for each module (or pack). _________________ Infralution Support |
|
Back to top |
|
|
codenut
Joined: 13 Apr 2005 Posts: 12 Location: Ontario Canade
|
Posted: Sat Apr 15, 2006 12:31 am Post subject: |
|
|
Infralution wrote: | Simply assign each module a one digit identifier eg
A = Basic Module
B = Advanced Module
C = Integration Module
For admin purposes I don't think you'd want any more than 10 anyway. Then your product info can simply be the list of purchased modules ie "AC" means they've purchased Basic Module + Integration Module. Because you don't want to have to remember this mapping you would create a custom user interface that just allows you to tick the appropriate check boxes and generates the ProductInfo for you - see the CustomGenerator sample project for an example. |
Okay I think I follow that and I will have a closer look at the customGenerator sample now - thanks
Infralution wrote: | The disadvantage is that if your payment/license issuing system is fully automated it is more difficult to manage cases where customers want to add extra modules (without paying for ones they have already purchased). |
Given the explanation provided I believe I will be going with a subscription module which basically allows for a single purchase for all during the current subscription period. The question is tho' how would the licensing handle renewals ?? would it be a new license issued? .. and how would you tell older subscription installs that they can't use the new ones .. would that be part of the "identifier" you mentioned above? _________________ Steven
WinExtra
http://www.winextra.com
news://news.winextra.com |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Sat Apr 15, 2006 12:38 am Post subject: |
|
|
If you want to do the subscription model then you would embed the expiry date in the ProductInfo - and then just check that against the current date. Of course you could also do both eg a license key with the following product info "AC;3/07" might mean you have licensed components A and C till March 07. Note that them license key size will increase the more information you put in ProductInfo - so generally you try to keep it succinct. _________________ Infralution Support |
|
Back to top |
|
|
codenut
Joined: 13 Apr 2005 Posts: 12 Location: Ontario Canade
|
Posted: Sat Apr 15, 2006 12:41 am Post subject: |
|
|
Infralution wrote: | If you want to do the subscription model then you would embed the expiry date in the ProductInfo - and then just check that against the current date. Of course you could also do both eg a license key with the following product info "AC;3/07" might mean you have licensed components A and C till March 07. |
Thanks guys .. appreciate the help and hopefully I figure it out right _________________ Steven
WinExtra
http://www.winextra.com
news://news.winextra.com |
|
Back to top |
|
|
|