David is making several good points. To address Bing's list directly:
- It sounds like Anukampa's concern is avoiding incomplete ticket
updates/transactions, as in:
A write transaction is not allowed without a valid license in the first
place. Therefore, you do not risk incomplete transactions. The only
thing that Anukampa may risk (if no licenses are currently available) is
to be prevented from saving at that specific time. You are either
allowed to make a complete transaction or nothing at all.
- User opens and begins to edit a ticket, pulling a floating
license
Ok
- User gets interrupted or otherwise distracted, and the floating
license expires
Ok, no damage done. Whatever work that has been done is still in the
form and can be saved at a later time.
- User's floating license is released, returns to the license pool,
and is subsequently reassigned to another user
Firstly: The license is only reassigned if another user that does not
have a licence in the first place performs an action that requires the
same type of license.
Secondly: A license, in this frame of reference, is a generic matter.
You do not need to acquire the exact same license - only one of the same
type, let's say for the Change application.
- User then tries to save the updated/edited ticket, but instead
receives an error message because the necessary floating license cannot
be re-acquired
Related to the previous point. The only thing that matters is that
another license of that type is available. If not, please wait until it
is:-)
Runar Helle
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David
Sent: 25. mai 2007 10:58
To: [email protected]
Subject: Re: Floating License Timeout
Isn't this only an issue only if the floating license pool isn't large
enough? If that's the case then one should be looking at a license
management solution.
Let's look at it a different way. If it was possible to provide the
warning message, what is the expected action by the user? Not save the
change because they may or may not get reassigned a license when the
save occurs? If they have made changes, discard them and login again to
see if they are granted a write license (another warning message if they
don't)?
Again I only see this as an issue if the license pool is not large
enough. Even if they get the error message when they attempt to do the
write, isn't chances of this smaller than the number of times they would
get the time out message?
When we have been extremely tight on licenses and our folks have gotten
the error message, if they waited 5 or 10 minutes they could attempt the
save again and often it would got through.
Dave
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Bradford Bingel
Sent: Friday, May 25, 2007 1:27 AM
To: [email protected]
Subject: Re: Floating License Timeout
**
It sounds like Anukampa's concern is avoiding incomplete ticket
updates/transactions, as in:
- User opens and begins to edit a ticket, pulling a floating
license
- User gets interrupted or otherwise distracted, and the floating
license expires
- User's floating license is released, returns to the license pool,
and is subsequently reassigned to another user
- User then tries to save the updated/edited ticket, but instead
receives an error message because the necessary floating license cannot
be re-acquired
Anukampa, is that correct?
-- Bing
Bradford Bingel ("Bing")
ITM3 California
http://www.itm3.com/
[EMAIL PROTECTED] (email)
925-260-6394 (mobile)
__20060125_______________________This posting was submitted with HTML in
it___ __20060125_______________________This posting was submitted with
HTML in it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
