Yes start using "only" starts using the stack, but what makes you
think the stack is not in memory while being in use?
If you want to use stacks in cgi's, you need to make sure they all
close before the cgi quits. It's just the way it is, and i don't know
exactly why. My guess is, that cgi's do not get the usual "cleanup"
stuff normal apps would get, for efficiencies sake. As you seem
reluctant to try if I'm actually right, here's an example handler you
can try:
#!revolution
global gDataA
on startup
start using stack "rocketscgi.rev"
put the defaultFolder into foo
cgiOutput foo
repeat for each line theLine in the openStacks
close stack theLine
end repeat
end startup
On 12 Mar 2008, at 09:07, Michael Doub wrote:
If the script was not terminating properly I would think that there
would
have been some output from the cgiOutput statement before script
terminated.
I don’t think that the "start using stack" statement is being
executed to
cause rockerscgi.rev to be loaded into memory. Note that the
cgiOutput
handler is identical in both cases except that in the failing case
it is in
a library stack vs being included in the same script.
-----Original Message-----
From: Richard Gaskin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2008 2:25 AM
To: How to use Revolution
Subject: Re: CGI's on a linux server
Björnke von Gierke wrote:
you need to manually (codially?) close every stack that you open in a
cgi, otherwise you get that error.
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
