Hello,
Today I noticed that QNetworkRequest/Reply insists on supplying a Content-
Length header in the request sent to the server. This has the drawback that it
is not possible to submit a POST/PUT body of indeterminate length. If a
sequential QIODevice is used as the request body input and Cont
You're correct in that it is reliable under the hood. The problem is really
just that most TCP APIs don't expose to the app what has been acknowledged. It
is pretty sad that everyone solves this by layering acks on top, when acks are
already being performed a layer down.
I think it would be nea
Hi,
It is not possible to know what TCP data has been acked through QTcpSocket
alone. The bytesWritten signal is more for flow-control. Generally speaking,
TCP is designed to make it easier to send data, but TCP alone is generally not
a solution for reliable transmission. It is possible to dete
On Monday, September 03, 2012 01:24:56 PM lars.kn...@nokia.com wrote:
> On Sep 2, 2012, at 3:57 PM, ext Thiago Macieira
wrote:
> > On domingo, 2 de setembro de 2012 22.23.01, Joseph Crowell wrote:
> >> QPixmap QPixmap::fromWinHICON( HICON ); Is there a reason this has been
> >> removed?
> >
> >
Hi,
I noticed that the buildkey of the official Qt Mac binary package is:
"macosx macx-cocoa g++-4 full-config"
However, when I built Qt Mac from source, I ended up with:
"macosx macx-cocoa g++-4 no-pkg-config"
Two questions:
1) Why would the existence of pkg-config during build have anythi
On Monday, August 13, 2012 07:33:53 PM Bob Hood wrote:
> On 8/13/2012 7:31 PM, Justin Karneges wrote:
> > Hi folks,
> >
> > It appears that MinGW's C++ ABI is not reliable between releases. I don't
> > know how often this happens, but in any case I
Regards,
> Alex
>
> On Mon, Aug 13, 2012 at 6:31 PM, Justin Karneges wrote:
> > Hi folks,
> >
> > It appears that MinGW's C++ ABI is not reliable between releases. I don't
> > know how often this happens, but in any case I've witnessed the
>
Hi folks,
It appears that MinGW's C++ ABI is not reliable between releases. I don't know
how often this happens, but in any case I've witnessed the following issue:
- Build machine has C:\Qt\4.8.2, built using a recent MinGW compiler. This
machine builds my application.
- User's machine has C:\
