Making kio_http more accessible to RESTful clients

[Thiago Macieira]

Josef Spillner wrote:
>Am Sonntag 05 Oktober 2008 21:16:20 schrieb Thiago Macieira:
>> POST is not supported by any other method. It's an HTTP-specific
>> method, handled by the "special" call.
>
>We either want to offer an abstraction layer with KIO, or we don't.
>From what I can see data can either be put somewhere, or it can be given
> to a service to do something with it. In this regard, a HTTP POST is
> highly similar to sending mail by SMTP or calling a SOAP operation.
> They all do something with data without any guarantee to give it back
> to you.

SOAP's HTTP transport is always POST. But that's just the transport: even 
for obtaining data it uses POST.

I would argue that SMTP sending (even according to your description) is 
"put", not "post". It sends something and maybe it'll give you a 
confirmation and an identification. That's all.

HTTP's POST is a special kind of operation that both uploads data and then 
downloads it. It's not something you'll easily find in other protocols. 
That's why it's "http_post" in KIO.

-- 
  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/88b413c6/attachment.sig>