Re: issue: SOAP requirements

[Dare Obasanjo <kpako@xxxxxxxxx>]

--- Joe Gregorio <joe.gregorio@xxxxxxxxx> 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.
> 
> I'm sorry, but I really don't see that as an issue,
> quoting from our charter:
> 
> "The feed format and HTTP will be used as the basis
> of work on a standards-track document specifying the
> editing
> protocol." [1]
> 
> A system that only allows GET and POST and strips 
> headers that it doesn't know about *is not* HTTP and
> I believe falls outside our charter.

At ETech, Sam Ruby made a comment about spec authors
needing to take responsibility for interoperability on
the Web. 

HTTP pedantry is all fine and dandy but if an option
exists that allows services that are being used by
millions of people to be Atom-enabled I don't see any
reason why they should be shut down. 

Nobody is saying that Atom shouldn't use REST with all
the HTTP verbs that half the developers out there
don't even know about. However many people on the
working group have stated at one time or the other
that SOAP is important for their scenarios. If you
don't have a technical reason for objecting to this
then I'd suggest that you be productive by helping in
fleshing out what is currently an underspecified
aspect of the spec. 

THINGS TO DO IF I BECOME AN EVIL OVERLORD #222
I reserve the right to execute any henchmen who appear to be a little too intelligent, powerful, or devious. However if I do so, I will not at some subsequent point shout "Why am I surrounded by these incompetent fools?!"


		
__________________________________ 
Do you Yahoo!? 
Make Yahoo! your home page 
http://www.yahoo.com/r/hs