CGI's and processing requests in order

[Gregory Lypny]

Hello Andre,

Thanks for confirming.  I also imagine that there's some kind of 
environmental variable that could be used as a token to distinguish 
among those instances of Revolution or the identity or addresses of the 
clients.

	Greg

On Sep 24, 2004, at 7:19 PM, Andre wrote:

> Gregory,
>
> I think that's the way everyone is doing, I use a token file to signal
> the busy state, so when I need to see if another instance of Rev is
> working, I just look for that file...
>
> Cheers
> andre
>
>
> On Sep 24, 2004, at 2:16 PM, Gregory Lypny wrote:
>
>> Hello everyone,
>>
>> In processing CGI requests, I understand that Revolution creates an
>> instance of itself in memory for each request.  I'm guessing that
>> because of this, it may be possible for two or more clients to be
>> accessing a text file almost simultaneously and create an update
>> anomaly if they both share information and have privileges to edit it.
>>  It's the situation where I need information that you can change and
>> you need information that I can change and you may change it to
>> something else when I'm still looking at the old stuff perhaps making
>> the wrong decision because of this.
>>
>> I'm curious to know what you think of a rough and ready way to queue
>> processing by having the CGI's access a file with a variable that is
>> either "busy" or "not busy".  The first request being processed sets
>> it to "busy".  If another client submits a request and the variable
>> comes up "busy", their page will be refreshed, perhaps with a brief
>> message, although it's probably not necessary given Rev's processing
>> speed, and when the variable is set back to "not busy", the next
>> client is processed.  Sound reasonable, or is it too clunky?
>>
>> 	Greg
>>