A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Waterfall_Cache has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 47

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 194

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Memcache_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 275

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Filesystem_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 440

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; APC_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 628

Take23: Do-Si-Do - "Locally" correcting to the secure port with mod_perl

Take23: Do-Si-Do - "Locally" correcting to the secure port with mod_perl

By ServerWatch Staff (Send Email)
Posted Mar 15, 2001


"The plus sign in +Apache::PortCorrect preloads the module. The rest of the statement declares the default function handler() in the specified module as code scheduled to be run immediately after receiving the request and building the request object, before bothering with anything else."

"mod_perl isn't really required to do this. I'm pretty sure you could do the same thing with mod_rewrite (an amazing piece of code....) But if you're already familiar with Perl, and want to get your hands into the server internals, this is the way to do that... and mod_perl also allows Apache::Registry, by which your Perl CGI scripts can be cached in server memory, eliminating all the spawn-and-parse overhead they would usually require, and allowing them access to Apache's internals via Apache::Request, and also giving you a door into lots of state management tools (since they share the server child's lifetime......)" ... if you're already familiar with Perl, and want to get your hands into the server internals, this is the way to do that... and mod_perl also allows Apache::Registry, by which your Perl CGI scripts can be cached in server memory, eliminating all the spawn-and-parse overhead they would usually require, and allowing them access to Apache's internals via Apache::Request, and also giving you a door into lots of state management tools ...

Page 1 of 1


Comment and Contribute

Your name/nickname

Your email

(Maximum characters: 1200). You have characters left.


 

 


Thanks for your registration, follow us on our social networks to keep up-to-date