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

[Richard Moore]

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.

On Thu, May 12, 2011 at 9:47 PM, Denis Kormalev
<kormalev.denis at gmail.com> wrote:
> Removing of QHttp and QFtp is of course needed, but it will be good if some
> features from them will appear in QNAM. For example I can name ability to
> set socket. It helps when you need to do http responses via already
> established channel (for example http is used only as subset of application
> network protocol and there are some other handshakes/commands/etc before
> sending http data).
>
> --
>
> Regards,
>
> Denis Kormalev
>
> _______________________________________________
> Qt5-feedback mailing list
> Qt5-feedback at qt.nokia.com
> http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
>
>