Mobile Platforms

However we would also like to licence a large number of mobile phones that connect to this desktop application.

Hey Jason,

There are a few ways you can do this, but it really depends on how you want to license the software on the mobile devices. For instance, if your mobile app is just a mobile version of your desktop app (that is, something they purchase but has no connection to the desktop app) then you're better off just using the licensing models built into the Windows Mobile or Andriod marketplaces. Android has its own licensing API built right into the marketplace. Similarly Windows Phone 7 has a much more limited licensing API built for their marketplace.

However if you're looking for a more versatile solution then we can help you write that. For instance, your desktop app could act as a "server" that only N licensed phones can connect to at one time.

I really need more information about how you'll be licensing the phones before I can guide you down the right path. But the short answer is: yes, we can help you do this.

Thanks for the links. We are currently investigating our licensing options.

The set up we have is that the mobile devices connect to the desktop application. We are currently working on what licensing model is best for our application.

At its simplest we want to limit the maximum number of mobiles connected to the desktop application at any time. This is the server with N licensed phones. The maximum number of mobile connections would be part of the licence on the desktop application. With this model we would want to be able to update the maximum number while the desktop application is in use. If we change the license (maximum number of connections) on the licence server ould this require us to do a Deactive(true) followed by Activate() to pull down the updated value?

Another possible licensing approach would require us to licence on a per mobile device where each device is uniquely identified, licenses would be reuired for each mobile and therefore the mobile would need to be identified as part of its activation.

If we change the license (maximum number of connections) on the licence server ould this require us to do a Deactive(true) followed by Activate() to pull down the updated value?

You don't have to call Deactivate(). Just call Activate() and the latest cryptographically-signed feature values will be downloaded. LimeLM handles all the details -- that is, it knows the computer is already activated and just resends the activation data with the latest feature data.