>>> For example, In the snippet above, you can see the newly added >>> Ns_ConnSockContent which returns a pointer to the read buffer (which >>> is otherwise private). Ordinarily the buffer would contain the HTTP >>> request line, any headers, then any body. You can get at the body with >>> the existing Ns_ConnContent. So if you just return "SYSLOG / >>> HTTP/1.0\r\n\r\n" and then your bytes in Recv(), the request would be >>> constructed and then you could parse the protocol beginning in the >>> body content. >>> >> >> I will try to take a look at this. ... >> > > > Did you take a look at this? What do you think?
I did and still did not come to any conclusions. The biggest concern is in order to make driver simple all drivers will be complicated and look like a hacks except nssock :-)) I want other dirvers to be first class citizens the same way as nssock which means driver needs to do a little be more than to be pure simple HTTP server. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
