Sylbert L wrote: > Thanks Stas, the code works just fine now. cool. I've fixed the online doc.
> This is what i'd read : > > [Apache 1.3 is hardwired to speak only one protocol, HTTP. Apache 2.0 has > moved to more of a "server framework" architecture making it possible to > plugin handlers for protocols other than HTTP. The protocol module design > also abstracts the transport layer so protocols such as SSL can be hooked > into the server without requiring modifications to the Apache source code. > This allows Apache to be extended much further than in the past, making it > possible to add support for protocols such as FTP, SMTP, RPC flavors and the > like. The main advantage being that protocol plugins can take advantage of > Apache's portability, process/thread management, configuration mechanism and > plugin API.] > > So if this is true, then shouldn't it be possible for me to implment a > constant connection using Apache 2.0 ? See my previous reply. You need to implement a protocol handler. Here is the URL again: http://perl.apache.org/docs/2.0/user/handlers/protocols.html > PS : Any idea when the API docs will be available ? We want to reuse as much of the C headers Apache docs as possible, Lyle is working on writing a tool which will extract them. I'm not sure what's the status of things. Perhaps Lyle can give us an update. Meanwhile, if you aren't sure what APIs to use look in the t/ directory, where there are a few hundreds of tests that exercise most of the existing APIs. Overall 1.3 methods aren't very different in 2.0, there are just a bunch of new methods which are new. Also you can reuse the Apache C documentation as well. See: http://docx.webperf.org and http://lxr.webperf.org/ __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
