Marcos Douglas wrote:
On Mon, May 24, 2010 at 2:24 PM, Lee Jenkins <l...@datatrakpos.com> wrote:
It is more or less a console application.
1. Request come in.
2. CGI Application starts and handles request through stdin/stdout.
3. CGI Application shuts down and release its resources.
One application is started and then shutdown for every request which comes
in. Not good for sites that need AJAX, connection pooling, persistent
objects, etc. Great (and fast) for sites with basic fetch(static, database,
etc) and display models, IMO.
Oh my...
Then I can do this:
var
s1, s2, s3: TStrings;
begin
s1 := TStringList.Create;
s2 := TStringList.Create;
s3 := TStringList.Create;
end;
...and at the end, no memory leaks?
This is true about Desktop (Win/Linux) apps too?
LOL. Well, you should always manage your resources regardless, though I think
you question was tongue in cheek.
I was talking more about the model of how it works.
--
Warm Regards,
Lee
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
