[Qt5-feedback] Network: QNetworkAccessManager vs QHttp/QFtp

[Denis Kormalev]

Haven't noticed that first email was not to list. Copying answer here.

I have stucked with such needance when we implemented support for upload 
continuing (by establishing connection from client to server and run simpliest 
http server at client-side). It took a really small amount of code and had 
good performance. But with QNAM we unable to do such things. I realize that it 
is really rare use case and provided another one that I think is more common.

-- 
Regards,
Denis Kormalev

On Friday 13 May 2011 at 01:54:44, Richard Moore <rich at kde.org> wrote:  

> I can't see that really being practical - modern HTTP involves
> multiple connections for pipelining, caching layers, proxies etc. If
> all you need is really a transport that pretends to be HTTP but is
> embedded in another protocol, then I'd suggest you really just want
> some custom code. In theory, one could expose the internal HTTP
> implementation of QNAM but that would make it much harder to improve
> the facilities in future whilst maintaining compatibility which would
> be a net loss for most uses.
> 
> Cheers
> 
> Rich.
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt.nokia.com/pipermail/qt5-feedback/attachments/20110513/c70a469e/attachment-0001.html