Le 13 oct. 2011 à 17:06, Maksymus007 a écrit :
On Thu, Oct 13, 2011 at 4:59 PM, Javier Guerra Giraldez <javier@guerrag.com> wrote:On Thu, Oct 13, 2011 at 9:52 AM, Maksymus007 <maksymus007@gmail.com> wrote:often because some years ago, REST wasn't a buzzword-compliant
> must works with some other solutions where choice of using SOAP over REST
> was made years ago.
acronym. anybody who suggested CRUD-over-HTTP (*) would've been
quickly vetoed out of the design committee meetings.
(*) yes, i know REST is totally not CRUD. tell that to those
'enterprise architects' in the '90s
True, but that how things are, nothing to argue more about. Django (and Python in general) do not like SOAP, and it's DJango problem, not SOAP, whatever some "cool developers who are typically to afraid of new things" say :/
Hi,
I hardly see where this is a Django problem. Microsoft (1) and Google (2) dropped SOAP support. This is a general move from the non pure java enterprises.
That put aside, if you are feeling Django is missing a proper SOAP support, you can still develop one.
If there's really a need for it for java world enterprises, you'll probably find help from others for that.
Xavier.
No comments:
Post a Comment