Greetings, Sorry to be late to the party, I didn't realize how this thread affected me until just this weekend. Sorry also for the extensive quoting, the thread is so old that I wanted to establish context.
Mon, 21 Apr 2003 10:52:57 -0500 Scott Goodwin wrote > The communication API has been simplified and is now one proc > that you register with the core server via Ns_DriverInit. > The core server manages reading and writing on the socket, > and the data read/written is passed through the single > function you register, all of which is piped > into the core server's HTTP processing. Mon, 21 Apr 2003 13:11:46 -0400 Vlad Seryakov <[EMAIL PROTECTED]> wrote: > Yes, API has been simplified but so much that only > HTTP protocol can be supported. On Mon, 21 Apr 2003 20:55:20 EDT, Jim Davidson wrote: > First of all, I'm guilty of removing the 3.x loadable driver > interface -- sorry about that. The old driver interface > was a feature of Naviserver 2.0 to support apps just like yours. On Wed, 23 Apr 2003 11:12:55 -0400, Vlad Seryakov <[EMAIL PROTECTED]> wrote: >I submitted patch #726288 for support of non-HTTp communication drivers. >Test was successfull, my SMTP module is working fine as in version 3. >Changes are minimal and should not affect the HTTP processing. Basically the removal of the comms api also breaks nsunix, which I was using in combination with nsvhr to provide virtual hosts. As has been discussed at length elsewhere on this list, one of the big advantages of nsunix is that it passes the actual FD of the socket, so the peer address of the client goes with it. That way don't need to do funky log tricks to get the peer address. I know that AOLserver 4.0 supports virtual hosting built in, but this method was quite clean and has the other side effect of enabling you to restart individual servers without downing your all your virtual servers at the same time. So I guess what I'm asking is if the core team has reviewed and considered Vlad's patch at all? --cro -- 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.
