On Thu, 24 Feb 2000, psahores wrote:
> The problem i try to avoid is to get the reusability of those "within
> metacard globals", without to have to reload them (from disk, 4Mo of
> text datas) each time a new instance of the ".mt" script is running. How
> to do to get them staying in a ram buffer betwin two instances of the
> ".mt" script. I think FastCGI do that but i d'nt now if it's friendly
> with Metacard and, perhaps, is it a best way to get the same result.
Running a MetaCard CGI should be no problem, performance-wise.
Loading a 4MB file would be though. We don't have any plans to
support FastCGI (or NSAPI or ISAPI or any of the other architectures
for doing this). You could build in support for it with Embedded
MetaCard, but if *I* were doing it, I'd use mchttpd and just direct
the CGI calls to a different port number on the server that goes
directly to the engine. This is going to be even faster than any of
these other alternatives and would be immensely easier to debug.
> Thank's Andu and sorry for my poor english :)
I think your English wasn't the problem, it was leaving out the small
detail that you were loading 4MB of data in your CGI ;-)
Regards,
Scott
> Pierre Sahores
>
> This is the MetaCard mailing list.
> Archives: http://www.mail-archive.com/metacard%40lists.best.com/
> Info: http://www.xworlds.com/metacard/mailinglist.htm
>
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
This is the MetaCard mailing list.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
