[snip] > > But, having recently perused a lot of Apache2 and mod_perl2 > documentation (including the recently-published mod_perl2 > User's Guide - thanks Stas & Jim), I now wonder if a better > idea would not be to use a dedicated Apache2/mp2 server for > the task, thus leaving all that complex multi-process > management to Apache. My document-retrieval code could just > go into a PerlResponseHandler. > > Any pearls of wisdom available so far ?
We have written both perl preforking and prethreading servers that have worked fine for us (prethreading a little less so). We now use apache as the daemon structure and have found it removes a lot of the pain. > Of course, if this document server is then a separate Apache > instance, all the application document links would have to be > rewritten as http:://this_other_server/getdoc/doc-id > and that is quite some work. (I also kind of dislike the > idea of the end-user browsers accessing the document-server directly.) > You don't have to use a http protocol we have our own protocol and just use apache for the daemon bit, google PerlProcessConnectionHandler And see http://perl.apache.org/docs/2.0/user/handlers/protocols.html HTH Iain.
