[Interest] Strange socket problem. QTcpSocket. Windows/Linux

[Thiago Macieira]

On segunda-feira, 27 de janeiro de 2014 10:24:22, Guido Seifert wrote:
> > My guess is that the TCP/IP stack on the D series TV is broken and is
> > somehow failing to deal with the packets from the Windows machine.
> 
> Yes, do you know if there is anything I can do? I don't see many options in
> QTcpSocket. What could be the difference between a Windows and a Linux
> socket? What I find interesting is that I have no problem with the stream
> itself. But the streaming socket is initiated by the TV itself.

If I'm right, then the problem has no solution inside Qt. It would imply 
trying to change something in the Windows socket stack to make it change how 
it sends the packets.

This is just a guess. I haven't seen the network traffic you have. I'm going on 
what you said ("the contents of the stream are identical") and the fact that 
if you remove the impossible, whatever remains, however improbable, must be 
the truth. If you remove the data, the only thing remaining is metadata and 
overhead.

> I am also a bit irritated that I have the problem with Windows. If the
> connection with Linux was broken... heck, which company tests their
> products for Linux compatibility? But Windows... this should not have gone
> unnoticed.

My guess? They didn't test much at all. They got some stripped down TCP/IP 
stack from somewhere, did some initial tests and shipped the product.

That's why companies are moving away from custom or specialised embedded OS to 
just running Linux on their hardware.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20140127/f4d8e943/attachment.sig>