> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of John Hester
> Sent: Thursday, February 16, 2006 6:26 PM
> To: [email protected]
> Subject: Re: [U2] Using keys for record locking with time 
> expirations...
> 
> 
> I think the locking mechanism you're describing could work.  
> If the key 
> is saved as a cookie on the client end you'll be able to get it back 
> with each transaction.  The main problem I see with using a 
> UV phantom 

I hadn't thought about using cookies to maintain the key, usually I
throw a HIDDEN field into the HTML code, so when the new page is processed
the key comes back. Yes, someone "could" modify the data. But as long
as I don't use sequential keys, that shouldn't be a problem. My reason
is that a lot of browsers might have cookies disabled.

> for processing requests is that it won't scale well past a single 
> simultaneous user.  If users A and B are simultaneously feeding 
> requests, there's no easy way to insure that A doesn't get 
> B's results. 

that won't be a problem, the UV interface doesn't know one user from
another, only to do what it's told. READ FILENAME ITEMNAME {ATT#}
the perl program takes care of keeping track what goes to who.
Since the interface is using SEQ files, it reads a command, does it,
gives the result using a SEQ write file.

In reality there isn't much data trasfer between UV and perl. Most of
the data handling will be done with the perl routine and between the
web sites.

>   You could possibly tag all requests and results with the 
> aforementioned key somehow, but it seems that could quickly get very 
> complicated.  If perl processes A and B are simultaneously 
> running, and 
> A get B's results, even if A realizes this, how are the 
> results going to 
> be handed to process B?  It would probably be much easier to 
> have each 
> cgi request launch a new uv process which would terminate as soon as 
> results are returned.
> 
> -John

George 
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to