Re: On GET_LOCK ()

[Paul DuBois]

At 4:36 AM -0500 7/28/99, <sinisa@stripped> wrote:
>toxalot@stripped writes:
> > >Hi Jennifer !
> > >
> > >
> > >There are indeed many ways this can be accomplished, but at this
> > >moment I think that the best possible way is with :
> > >
> > >select get_lock("user_name",10000);
> > >.........
> > >
> > >select release_lock("user_name");
> > >
> > >
> > >If you have further questions, please do not hesitate.
> > >
> > >Sinisa
> > >
> >
> >
> > When would you select release_lock ?  Would users have to log out and then
> > you could select release_lock?
> >
>
>Hi Jenifer !
>
>What I was suggesting to you is the algorithm to use in your programs
>or applications.
>
>
>When the user logins, you run get_lock with a high timeout value, This
>value should be empirical, because customer may switch off, and a lock
>would remain to ban further entry.

I don't understand this.  If by "switch off" you are referring to the
person with the original lock, when that user's session ends, the lock
is automatically released.  If you are referring to the second person
who requests the lock, won't the request be tossed if that session is
killed?

--
Paul DuBois, paul@stripped