Thiago, Thanks for your reply.
It happens that the problem was in program B because it was also using libimobiledevice. This is a C lib used to talk with iOS devices. It happens that it’s internal mechanisms were blocking the program execution and consequently the sockets data flow. I have only realized that when tried to create a standalone example to share with the list. The example I was producing didn’t had the problem I was observing. The obvious solution for this problem was to run the classes that invoked libimobiledevice calls in another thread. There is no problem anymore. Sorry if the description was not completely clear but I didn’t want to create even more confusion explaining all that was involved. Regards, Nuno > On 24/04/2015, at 16:56, Thiago Macieira <thiago.macie...@intel.com> wrote: > > On Friday 24 April 2015 12:01:10 Nuno Santos wrote: >> Hi, >> >> I have passed the last 48 hours trying to understand a problem I was having >> with sockets. I was driving crazy but I think I finally reached a >> conclusion. Let me summarize: >> >> - Program A that sends data via sockets to localhost >> - Program B, built in Qt, receives data via QUdpSocket (I have also tried >> with QTcpSocket and the problem is the same). >> >> Program A sends constant size messages (76 bytes) each 60 ms. >> Program B receives the message and prints the latency between the current >> message and the last message. > > Let's stop here. There's one too many programs in the description. > > Please tell us whether the problem is in program A or in program B. You need > a > traffic sniffer/analyser to do that. Tell us whether the packet is being sent > at > the correct time by program A. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest