ABorka wrote:
Did. But in the current economy the traffic is down, and because of CGI
doesn't require an Apache restart when anything changes in the app, we
are just using CGI at the moment (with HTML templates and template tags
using fpTemplate). Did not see speed difference between the two.
On Thu, May 20, 2010 at 3:21 PM, ABorka fpc-de...@aborka.com wrote:
(...)
However, any time the need arises, we can just recompile the app as an
Apache module in minutes and us that.
The web module source code is exactly the same for CGI programs and Apache
mods, so no changes needed for the
On 5/22/2010 08:27, Marcos Douglas wrote:
(...)
However, any time the need arises, we can just recompile the app as an
Apache module in minutes and us that.
The web module source code is exactly the same for CGI programs and Apache
mods, so no changes needed for the recompile at all.
No
On Sat, May 22, 2010 at 4:13 PM, ABorka fpc-de...@aborka.com wrote:
We write all code as if it were an Apache module (or FCGI), even if we
compile it as CGI at the moment.
You just need to take care of the fact that web modules already in the
memory can be reused for following requests (in
OK, since everyone's talking about the web technologies in Laz/FPC lately, I
have a question. Anyone currently running web site/app with WebLaz Apache
module flavor. Any high traffic?
I'm using a stand alone synapse based HTTP server now for testing, but I want to
deploy eventually to
Did. But in the current economy the traffic is down, and because of CGI
doesn't require an Apache restart when anything changes in the app, we
are just using CGI at the moment (with HTML templates and template tags
using fpTemplate). Did not see speed difference between the two.
However, any