Execute method in the server side.

[Harjo]

oke, but I quote Paul here:

I don't think so Harjo, for the duration of the execution of the code in the authenticator solution (so a fraction of a second, if you do it properly), a license is consumed.

Does that mean, if you have 10 licenses, and 9 are logged in, the 10th can't be logged in? because his login solution needs a license AND his authenticator needs one (a fraction of a second) or am I seeing bears here?

[Thomas Parry]

Good question Harjo - we would not like to see a license consume solely for login that cannot be re-used for subsequent solution usage.

[pbakker]

You're seeing bears indeed, as we allow the server to go over it's license limit for short periods, so this isn't really an issue.

Paul

[Thomas Parry]

SO, Paul, now that you have opened up the discussion...
We would like to know what this short time threshold really is?
Can it be exploited to do more than the login? (Not that I would use that of course).
Just want to be clear on the length of time that login can take - if for instance there is a "slow" internet connection.

[pbakker]

Hi Thomas,

Which discussion did I start? The threshold is sufficient for slow login connections.

Paul