Qt-interest Archive, May 2007
QTcpSocket/QTcpServer and Out of Band Data
Message 1 in thread
How does QTcpSocket and QTcpServer handle out of band data? Is all
the data in band, can you tell which data received is oob, can you
send oob data?
Thanks,
Robert
--
[ signature omitted ]
Message 2 in thread
> How does QTcpSocket and QTcpServer handle out of band data? Is all
> the data in band, can you tell which data received is oob, can you
> send oob data?
>
> Thanks,
> Robert
TCP data is always "in band"!
Maybe you're thinking of "urgent data" - a concept that is kind of
broken and afaik not handled by Qt.
Cheers,
Peter
--
[ signature omitted ]
Message 3 in thread
On 5/11/07, Peter Prade <prade@xxxxxxxxxxx> wrote:
> > How does QTcpSocket and QTcpServer handle out of band data? Is all
> > the data in band, can you tell which data received is oob, can you
> > send oob data?
> >
> > Thanks,
> > Robert
>
> TCP data is always "in band"!
> Maybe you're thinking of "urgent data" - a concept that is kind of
> broken and afaik not handled by Qt.
>
In Winsock and Linux you make the following calls to make all out of
band data (marked urgent) inline (receives OOB data in the normal data
stream):
int value = 1;
::setsockopt(socket, SOL_SOCKET, SO_OOBINLINE, (const char *) &value,
sizeof(int));
Sound like Qt doesn't handle urgent data at all, which is unfortunate
because some protocols (like telnet) make use of OOB/urgent data.
--
[ signature omitted ]
