Re: CGI's and processing requests in order

[Richard Gaskin]

Sannyasin Sivakatirswami wrote:
Interesting... I was just about to open up a similar OT thread
"Does anyone know of a Rev GUI to act as an RCS for CVS"
There are several, and it's not hard to roll your own if needed.  That 
is, as long as you're more interested in results than theory:  there was 
a long thread here last year on the topic and it got bogged down in 
atomizing all scripts and properties.  But in practical terms there's 
little need for that:  well-factored projects and well-structured 
workflows will favor a stack-level check-in/check-out; anything more 
finely grained is likely overkill, and arguably a case of diminishing 
returns.

Chipp Walters made a nifty commercial check-in/check-out tool:

Ken made a simpler one a while back for a project he's working on.
I made a specialized one in an afternoon to support 20 contributors on 
three continents for a client's Rev-based database.

With libURL's FTP there's almost nothing you can't do for a useful 
check-in/check-out system

--
 Richard Gaskin
 Fourth World Media Corporation
 ___
 [EMAIL PROTECTED]   http://www.FourthWorld.com
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: CGI's and processing requests in order

[Andre Garzia]

Sannyasin,
Take a look into Magic Carpet by Altuit, it's a wonderfull Version 
Control System, can be used as a plugin in Rev and do everything you 
said in your tread. I am using it here, and I'll never touch CVS 
again... =)

Cheers
andre
On Sep 25, 2004, at 2:25 AM, Sannyasin Sivakatirswami wrote:
Aloha,
Interesting... I was just about to open up a similar OT thread
"Does anyone know of a Rev GUI to act as an RCS for CVS"
In my context I'm interesting in keeping a repository of specification 
documents, task rosters etc.   easily viewable and searchable as .html 
docs on the web site.  Certain team players would have editing 
privileges, and could view them and if they wanted to edit, click a 
button and edit, but other users would be locked out if an edit was in 
progress. The system should have an option to add comments if 
possible, not only to the document, but as a kind of meta data to the 
document itself, which detailed briefly the nature of the revision 
update.

like "Andre: I just added new criteria for the transcription process."
Adobe has added all this functionality to their CS suite "Version 
Cue"... and, though it's slow and clunky, it works. A rev version for 
a html/web repository would be lightening fast.

I don't know if this what you are doing by it seems to be a related 
area... btw the "token" is sometimes referred to also as a "semaphore 
file"

A Rev widget, standalone editor to interface with the site would be 
equally acceptable (for those having editing privileges) as the html 
docs will be very simply formatted, well within the range of Rev's 
HTML tag set.

I'm sure this has wheel has been rolled before...of course the cmd 
line is there for wizards who can do the RCS thing from the unix cmd 
line if they have root access to the server, but this won't work for 
"secretary" level users, who just know how to type and click. And the 
security issue would never allow for expansion of the number  of 
people with root access, so a GUI is needed to have more team players 
with edit privileges.

But, perhaps you user role here is completely something other than 
what I'm describing.

Sannyasin Sivakatirswami
Himalayan Academy Publications
at Kauai's Hindu Monastery
[EMAIL PROTECTED]
www.HimalayanAcademy.com,
www.HinduismToday.com
www.Gurudeva.org
www.Hindu.org
On Sep 24, 2004, at 1:30 PM, Gregory Lypny wrote:
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
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

--
Andre Alves Garzia  2004  BRAZIL
http://studio.soapdog.org
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: CGI's and processing requests in order

[Gregory Lypny]

Yes, yours is much more ambitious, although the idea is essentially the 
same.  For mine, users read and write the same data because they will 
be participating in a variety of markets: auctions, continuous double 
auctions (like stock markets), bi-lateral trade.  So, offers 
necessarily change the market price at which everyone transacts.

Greg
On Sep 25, 2004, at 12:01 PM, Sannyasin wrote:
Interesting... I was just about to open up a similar OT thread
"Does anyone know of a Rev GUI to act as an RCS for CVS"
In my context I'm interesting in keeping a repository of specification
documents, task rosters etc.   easily viewable and searchable as .html
docs on the web site.  Certain team players would have editing
privileges, and could view them and if they wanted to edit, click a
button and edit, but other users would be locked out if an edit was in
progress. The system should have an option to add comments if possible,
not only to the document, but as a kind of meta data to the document
itself, which detailed briefly the nature of the revision update.
like "Andre: I just added new criteria for the transcription process."
Adobe has added all this functionality to their CS suite "Version
Cue"... and, though it's slow and clunky, it works. A rev version for a
html/web repository would be lightening fast.
I don't know if this what you are doing by it seems to be a related
area... btw the "token" is sometimes referred to also as a "semaphore
file"
A Rev widget, standalone editor to interface with the site would be
equally acceptable (for those having editing privileges) as the html
docs will be very simply formatted, well within the range of Rev's HTML
tag set.
I'm sure this has wheel has been rolled before...of course the cmd line
is there for wizards who can do the RCS thing from the unix cmd line if
they have root access to the server, but this won't work for
"secretary" level users, who just know how to type and click. And the
security issue would never allow for expansion of the number  of people
with root access, so a GUI is needed to have more team players with
edit privileges.
But, perhaps you user role here is completely something other than what
I'm describing.
Sannyasin Sivakatirswami
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: CGI's and processing requests in order

[Sannyasin Sivakatirswami]

Aloha,
Interesting... I was just about to open up a similar OT thread
"Does anyone know of a Rev GUI to act as an RCS for CVS"
In my context I'm interesting in keeping a repository of specification 
documents, task rosters etc.   easily viewable and searchable as .html 
docs on the web site.  Certain team players would have editing 
privileges, and could view them and if they wanted to edit, click a 
button and edit, but other users would be locked out if an edit was in 
progress. The system should have an option to add comments if possible, 
not only to the document, but as a kind of meta data to the document 
itself, which detailed briefly the nature of the revision update.

like "Andre: I just added new criteria for the transcription process."
Adobe has added all this functionality to their CS suite "Version 
Cue"... and, though it's slow and clunky, it works. A rev version for a 
html/web repository would be lightening fast.

I don't know if this what you are doing by it seems to be a related 
area... btw the "token" is sometimes referred to also as a "semaphore 
file"

A Rev widget, standalone editor to interface with the site would be 
equally acceptable (for those having editing privileges) as the html 
docs will be very simply formatted, well within the range of Rev's HTML 
tag set.

I'm sure this has wheel has been rolled before...of course the cmd line 
is there for wizards who can do the RCS thing from the unix cmd line if 
they have root access to the server, but this won't work for 
"secretary" level users, who just know how to type and click. And the 
security issue would never allow for expansion of the number  of people 
with root access, so a GUI is needed to have more team players with 
edit privileges.

But, perhaps you user role here is completely something other than what 
I'm describing.

Sannyasin Sivakatirswami
Himalayan Academy Publications
at Kauai's Hindu Monastery
[EMAIL PROTECTED]
www.HimalayanAcademy.com,
www.HinduismToday.com
www.Gurudeva.org
www.Hindu.org
On Sep 24, 2004, at 1:30 PM, Gregory Lypny wrote:
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
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: 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
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: CGI's and processing requests in order

[Andre Garzia]

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
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

--
Andre Alves Garzia  2004
Soap Dog Studios - BRAZIL
http://studio.soapdog.org
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

CGI's and processing requests in order

[Gregory Lypny]

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
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution