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

Thiago Macieira thiago at kde.org
Fri May 13 00:25:47 CEST 2011


On Thursday, 12 de May de 2011 22:54:44 Richard Moore 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.

I agree here.

When I started reading the email, I thought the suggestion would be about 
adding the FTP commands that QNAM currently doesn't support. That's what I 
pointed out in today's blog, that we're open for suggestions on how to 
implement that cleanly. For example, I like the KIO architecture of job 
classes, but I don't think that's very "Qtish" -- too many levels of 
inheritance.

What you're suggestion, though, about giving you access to the socket and 
being able to do things that the HTTP spec doesn't even allow for, sorry, I 
don't agree. The internals of the HTTP engine mean that there are multiple 
sockets that can be open at any one time. You simply don't know if, for your 
request, the request will be sent on an already-opened socket or whether it 
will be opened anew. Or if a resending will be necessary because of a proxy 
authentication.

If you need to do something that is not on the HTTP spec, then I'd say that 
you don't have HTTP and QNAM is not trying to solve your problem. You'll need 
to roll out your own code.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt.nokia.com/pipermail/qt5-feedback/attachments/20110513/24a63c8d/attachment.bin 


More information about the Qt5-feedback mailing list