I assume that "fat mod_perl authenticating servers" means yes the memory footprint is significant enough to cause issues.
At this point I would prefer to keep the existing authentication system which is a simple md5 hash. The perl handler was to decode and test the hash to see if it is still valid. Then if so allow the server to continue to the "real" uri
Cookies introduce a whole new level of problems. Considering that our media server are ip based and many browsers and media players etc wont send a cookie to an ip address.
That is why we never used cookies to begin with. otherwise we could have done that from the originating server.
Given that would fastcgi be a better choice. I could authenticate the user then respond with a X-sendfile header. once authentication is done the socket is dropped and I no longer need to worry about the "memory overhead" allowing the trim apache server(or lighttpd) to process the request as per normal
In reply to Re^2: mod_perl memory footprint
by DeveloperChris
in thread mod_perl memory footprint
by DeveloperChris
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |