KIO: separating the API from the implementation

[David Faure]

On Wednesday 21 March 2007, nf2 wrote:
> why is "get" and "put" handled by the same class "TransferJob", although 
> a "get" job will never emit a "dataReq" signal and a "put" job will 
> never emit a "data" signal? Having separate "GetJob" and "PutJob" 
> classes would probably make the API easier to understand...

There would be quite some duplication between GetJob and PutJob though:
redirection handling, suspend/resume, metadata. So there would need to be 
a base class, maybe called TransferJob ;).
In addition, it's not just get and put, it's get+put+http_post.
The benefit would be quite marginal IMHO, but why not.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).