[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: issue: SOAP requirements

Assuming all we can do is GET/POST, a solution would be multiple service
URLS that only use GET/POST (in each entry)  rather than a single Edit service
that does everything (GET/POST/PUT/DELETE). For example, there could
be an update URL, a delete URL and a read URL. Posting to the delete URL
would delete the entry. Posting to the update URL would update the entry.

I know this is not strictly RESTable, but it allows all of the basic operations
using only GET/POST, fits within the constraints of a phone client and does
not require custom headers.

Brett Lindsley, Motorola Labs

Tatsuhiko Miyagawa wrote:
Some mobile phone clients (like DoJa[1], NTT DoCoMo i-mode Java) can't
send customized HTTP headers. And I've heard there're some mobile
gateway servers that strip out all of them, even if agents can set.

With SOAP version of Atom, you can put HTTP verbs and WSSE auth stuff
into the SOAP envelope.

[1] http://www.doja-developer.net/

On Thu, 17 Mar 2005 14:48:46 +0200
Janne Jalkanen <jalkanen@xxxxxxxxx> wrote:

  
The PaceAtomActionHeader does it all for J2ME with a lot less hassle
than SOAP (and has the added advantage of not needing base64).

I don't like SOAP either.  Too much excess baggage.

/Janne


On Wed, 16 Mar 2005 23:56:31 -0800, James M Snell <jasnell@xxxxxxxxx> wrote:
    
Tim Bray wrote:
 > On Mar 16, 2005, at 8:52 PM, James M Snell wrote:
 >
 >> Better question: why bother with SOAP at all?  Either make the Atom
 >> API a SOAP based thing or don't.  I vote for getting rid of the SOAP
 >> option altogether unless someone can step up and give a solid defense
 >> for why it is absolutely necessary to be able to support such a thing.
 >