On Tue, 2004-08-17 at 03:59, Andrew Piskorski wrote: > On Tue, Aug 17, 2004 at 10:32:56AM +0200, Zoran Vasiljevic wrote: > > > Vlad's patch implements entirely new socket-level driver and sticks > > the whole add-in functionality in the driver itself, effectively > > > Stephen's patch integrates into the AS by adding new API call > [...] > > from a connection socket. This way a new protocol connect handling > > looks pretty much like regular http. Hence it utilitzes all of the > > Are there any types of protocols that Vlad's approach can handle while > Stephen's cannot? E.g., protocols that look very different from HTTP? > If so, would it make sense to support BOTH methods in AOLserver?
Although the example protocol driver for POP3 generates what looks like a (basic) HTTP request, there is no requirement to do so, it was just convenient. If you were handling some binary protocol, the minimum you would have to do in the parse proc would be identify the end of the message, and set the request line 'MYPROTO /'. You would then register a proc for that method and URL which calls Ns_ConnContent to get access to the payload of the message. The request line becomes a dummy, but it may still be useful. For example you can use it to force processing from one or another connection pool. There is the restriction at the moment that protocols which require pipelining (sending message 2 before receiving the answer to message 1), and by extension protocols which don't need an answer to all requests, aren't supported. I'd like to add that though, it's a requirement of HTTP/1.1 and a handy speed boost. > Also, this is all still only for protocols on top of TCP/IP, right? > No support for UDP or any other sort sockets? Vlad has submitted a patch which adds support for this to the binder: http://sourceforge.net/tracker/index.php?func=detail&aid=463625&group_id=3152&atid=353152 I think the most useful feature here would be unix domain sockets for something like a fastcgi module. This would be transparent to existing socket drivers. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
