>>> 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 exis
On Wed, Oct 22, 2008 at 10:35 PM, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
static ssize_t
Recv(Ns_Sock *sock, struct iovec *bufs, int nbufs, Ns_Time
*timeoutPtr, int flags)
{
static const char request[] = "GET /whateva HTTP/1.0\r\n\r\n";
size_t requestLen = siz
I will try to take a look at this. With new API i could not figure out
about pre-apending request data in Recv callback, so i had to come up
with the solution which is almost the same as before.
It is just that now i need in my driver to keep track when actual binary
data starts and i have to f
On Wed, Oct 22, 2008 at 8:36 PM, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
>>
>> static ssize_t
>> Recv(Ns_Sock *sock, struct iovec *bufs, int nbufs, Ns_Time
>> *timeoutPtr, int flags)
>> {
>> static const char request[] = "GET /whateva HTTP/1.0\r\n\r\n";
>> size_t requestLen = sizeof(reques
>
> static ssize_t
> Recv(Ns_Sock *sock, struct iovec *bufs, int nbufs, Ns_Time
> *timeoutPtr, int flags)
> {
> static const char request[] = "GET /whateva HTTP/1.0\r\n\r\n";
> size_t requestLen = sizeof(request);
> socklen_t sockLen = sizeof(struct sockaddr_in);
>
> memcpy(bufs->
On Wed, Oct 22, 2008 at 4:23 AM, Vlad Seryakov
<[EMAIL PROTECTED]> wrote:
> Update of /cvsroot/naviserver/naviserver/nsd
> In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv22913/nsd
>
> Modified Files:
>driver.c
> Log Message:
> new accept status, SSL driver works now
>
>
> Index: driv
