On Wed, 7 Jul 2010, Andrew Brunner wrote:
Well... I think CGI gateway is a good way. If the real app (FCGI) have
troubles, I can change the URL that the CGI (gateway) uses to call the
real app and to point to another app (in other server, e.g.). What do
you think about it?
I think it would be worth discussing what can be done or at least
start thinking about getting the memory manager not to blow-out any
more. I really don't want to re-start server software just because a
few apps (embedded in the service application) crash.
Has anyone with experience with developing the memory manager been
following? What about a separate discussion on application
stabilization after an unhanded exception? That would be a necessity
for at least my platform which is compiled with FPC - and certainly
FCLWeb generated back-end apps too.
Fcl-web ? Why ?
1. All fcl-web backends handle exceptions that occur in the web-request handler.
2. There is never an excuse for not freeing allocated resources, also in cases
of
exceptions. Such leaks must be identified, and plugged. Not worked around.
FPC offers the heaptrace unit exactly for this.
There is no way to allocate, use (and subsequently automatically free)
memory associated with a web-request. One reason is simply string and
class instance management, both of which inherently rely on a global
heap manager without concept of 'context'.
Michael.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
