Making kio_http more accessible to RESTful clients

[Thiago Macieira]

On Monday 06 October 2008 09:02:19 Josef Spillner wrote:
> At an abstract level, to avoid confusion, my suggestion is to use a naming
> which reflects the difference of storing vs. processing. That is all.

When KIO was designed, back in KDE 2 days, the semantic was that which I 
described. There was no REST those days.

And SMTP isn't really a filesystem, so someone chose to implement the sending 
of email using the standard "put" operation. You may notice that there's no 
"get" for SMTP.

In any case, libkio went mostly untouched for the KDE 4 porting effort. Aside 
from the porting to Qt 4 and KDE 4 lower libraries, plus a cleaning up that I 
did, nothing happened.

Given that track record, I expect KDE 5's KIO to be exactly like that again. 
Mostly because it just works and it isn't "sexy" to touch the I/O internals.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20081006/3cd90672/attachment.sig>