On Tuesday 17 August 2004 11: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?
Both approaches can handle arbitrary TCP protocols. > > Also, this is all still only for protocols on top of TCP/IP, right? > No support for UDP or any other sort sockets? Stepens patch sits atop of existing nssock driver hence it is doing any protocols nssock can (TCP only for now). But there is nothing which forbids you to make a UDP-level socket driver and integrate it in the AS and then use Stephens patch to add your own upper-level processing. Vlad's patch does replace the nssock entirely, leaving you to implement whatever you want in the driver. It has very limited interaction to AS machinery really. Zoran -- 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.
