[evla-sw-discuss] An "In Use" flag for the MIB interface

[Kevin Ryan]

Hichem,

I think this is an excellent implementation of the lock - it is nice  
and simple.

Are there situations where two different processes on the same client  
would conflict (they would have the same IP address)?

'Left on locks' should simply be handled like they are in the real  
world; by policy -- "Anyone neglecting to remove his lock shall be  
punished by not more than 6 months of attending code-walkthroughs"   
It would be complicated to implement software that could prevent left- 
on-locks.

Also, I don't think I understand what you mean by the servlet/applet  
thing not working.  Servlets, at least, should work because they have  
knowledge of the remote client's IP address.  And I would think  
Applets could send the client's IP back to the remote server (the MIB).

Or am I misunderstanding something?

Kevin


On Aug 15, 2006, at 12:04 PM, Bill Sahr wrote:

>
> Any application that locks through a servlet or applet is not  
> guaranteed
> to have exclusive use of a lock because all other applications going
> through the same servlet or application will be seen as having set the
> lock, i.e., will have the same originator IP address (the password).