The lifetime of the cache used by ServerManagedPolicy is controlled by the server (as the name suggests), and has three variables:
VT | License validity timestamp. Specifies the date/time at which the current (cached) license response expires and must be rechecked on the licensing server. |
GT | Grace period timestamp. Specifies the end of the period during which a Policy may allow access to the application, even though the response status is RETRY. The value is managed by the server, however a typical value would be 5 or more days. |
GR | Maximum retries count. Specifies how many consecutive RETRY license checks the Policy should allow, before denying the user access to the application. The value is managed by the server, however a typical value would be "10" or higher. |
This is documented here: http://developer.android.com/guide/publishing/licensing.html#extras
--
Trevor Johns
Google Developer Programs, Android
On Sat, Jul 31, 2010 at 7:23 AM, sblantipodi <perini.davide@dpsoftware.org> wrote:
Hi,
I'm using the ServerManagedPolicy implementation from the LVL code
sample (MainActivity.class) but I haven't understood how it manage
cache.
The first time application start it needs internet to validate the
license, if it is validated, how much time should pass before a second
check is needed?
Thanks.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment