Hi,
I see some info in the doc but it is not clear to me that whether select can
be made to wait on proxy (together with other sockets). Is it possible?
Another question, I see that after select returns reading on the socket
returns always 16 bytes even though I’m requesting more and I’m pumping data
to socket in a way that it should have more. Is this by design or this can
be changed?
Thanks,
Hakim
“Hakim” <ddrv2002@yahoo.ca> wrote in message
news:d9brr2$j6c$1@inn.qnx.com…
Hi,
I see some info in the doc but it is not clear to me that whether select
can be made to wait on proxy (together with other sockets). Is it
possible?
Yes look at implementing/replacing _select_received, documented in select()
Another question, I see that after select returns reading on the socket
returns always 16 bytes even though I’m requesting more and I’m pumping
data to socket in a way that it should have more. Is this by design or
this can be changed?
TCP/IP is a streaming protocol, expecting data in certain block size is an
error in design. Your code should handle any size.
Thanks,
Hakim
TCP/IP is a streaming protocol, expecting data in certain block size is an
error in design. Your code should handle any size.
Yes.
To clarify, say I’m making a request of 1460 bytes on read and read always
returns 16 bytes of data. Why is it is always 16 bytes? I expect it to
return different sizes but it stays same. From the other end data is being
fed continuously so socket should have data available of varying sizes. One
thing is that may be select and read in such a seuquence that socket doesn’t
have data more than 16 bytes.
Thanks,
Hakim
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:d9c688$qbo$1@inn.qnx.com…
“Hakim” <> ddrv2002@yahoo.ca> > wrote in message
news:d9brr2$j6c$> 1@inn.qnx.com> …
Hi,I see some info in the doc but it is not clear to me that whether select
can be made to wait on proxy (together with other sockets). Is it
possible?Yes look at implementing/replacing _select_received, documented in
select()
Another question, I see that after select returns reading on the socket
returns always 16 bytes even though I’m requesting more and I’m pumping
data to socket in a way that it should have more. Is this by design or
this can be changed?TCP/IP is a streaming protocol, expecting data in certain block size is an
error in design. Your code should handle any size.
Thanks,
Hakim
“Hakim” <ddrv2002@yahoo.ca> wrote in message
news:d9c9fv$smi$1@inn.qnx.com…
TCP/IP is a streaming protocol, expecting data in certain block size is
an error in design. Your code should handle any size.Yes.
To clarify, say I’m making a request of 1460 bytes on read and read always
returns 16 bytes of data. Why is it is always 16 bytes? I expect it to
return different sizes but it stays same. From the other end data is being
fed continuously so socket should have data available of varying sizes.
One thing is that may be select and read in such a seuquence that socket
doesn’t have data more than 16 bytes.
You should read until there is 0 byte left (in a while loop), indeed select
could return when there is 16 bytes in the buffer.
Thanks,
Hakim“Mario Charest” postmaster@127.0.0.1 wrote in message
news:d9c688$qbo$> 1@inn.qnx.com> …“Hakim” <> ddrv2002@yahoo.ca> > wrote in message
news:d9brr2$j6c$> 1@inn.qnx.com> …
Hi,I see some info in the doc but it is not clear to me that whether select
can be made to wait on proxy (together with other sockets). Is it
possible?Yes look at implementing/replacing _select_received, documented in
select()
Another question, I see that after select returns reading on the socket
returns always 16 bytes even though I’m requesting more and I’m pumping
data to socket in a way that it should have more. Is this by design or
this can be changed?TCP/IP is a streaming protocol, expecting data in certain block size is
an error in design. Your code should handle any size.
Thanks,
Hakim
\