On Wed, 17 Mar 2010, Michael Schnell wrote:
On 03/15/2010 08:54 PM, Joost van der Sluis wrote:
Fcl-web is a framework on which you can make 'anything' you want. You
can use FCGI and your program will be persistent. You can use the
webmodules. If you do, you can let the framework create a new webmodule
for every call. (REST) But you can also make them persistent. You can
even bind them to one session. So you have one Webmodule persistent in
memory for every session.
I don't understand how this can work.
If you install you CGI on a hired web server, same will not provide a
GUI APi, so you can't do this program as a normal "Application" e.g.
with GTK binding.
If you therefor use the "nogui" Widget Type, the program can't handle
events and thus will stop as soon as the user code is done. Thus it is
not "persistent".
Why not ?
It just has to persist all variables it needs in the next request.
The session takes care of that.
It doesn't have a queue, though. Because the web-server handles that.
(Each http-request is an event)
How are such events communicated from the web server to the CGI program
? What mechanism "fires" these events within the GCI code ? How is the
program supposed to wait for such an event ?
It just waits for a request on the socket.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
