Re^6: CGI and persistent data

Replies are listed 'Best First'.
Re^7: CGI and persistent data by bv (Friar) on Sep 01, 2009 at 01:54 UTC
Unfortunately, I haven't used FastCGI myself, so I can't produce code, but my understanding of the process is this: A FastCGI program runs persistently, handling its own forking, and communicates with the Web server over a socket. A regular CGI app is run from scratch every time it is invoked, but a FastCGI is already running (and can have its own objects in memory) when the Web server hands of a request to it. See FastCGI for more info, and check FastCGI for modules. `print pack("A25",pack("V*",map{1919242272+$_}(34481450,-49737472,6228,0,-285028276,6979,-1380265972)))`	[reply] [d/l]
Re^8: CGI and persistent data by astroboy (Chaplain) on Sep 01, 2009 at 21:19 UTC
I'm not sure this will solve the OP's problem. If the FastCGI program saves its state to some global variables between requests, the next request might be from a different user. I think you'll still need to maintain session state that will be tied to a specific user	[reply]
Re^9: CGI and persistent data by bv (Friar) on Sep 01, 2009 at 22:31 UTC
True, you'll need to maintain session state yourself. A trivial example (that has plenty of bugs): `print "<p>Hello, ", $session{$cookie}->{name}, ", welcome back</p>"` [download] `print pack("A25",pack("V*",map{1919242272+$_}(34481450,-49737472,6228,0,-285028276,6979,-1380265972)))`	[reply] [d/l] [select]