> In some ways, this continuing debate about REST amounts to a > suggestion to use HTTP everywhere and for everything.
I would hesitate to say it should be used everywhere. The problem I see is people ignoring HTTP where it could be used. Instead they are using other things (e.g. SOAP) that are then more difficult to integrate into the world of HTTP. The debate in my head, if nowhere else, is when is it not appropriate to use HTTP. And so... > However as was pointed out during the W3C debate (by users, not > vendors by the way) HTTP and URI based protocols are insufficient > for use within the firewall. The Web of documents, as REST is > usually called within the W3C community, may be great for publishing > and distributing corporate data but not so great for updating it or > securing access to it. That's curious. Pointers to more information? There are web applications inside the firewall here that secure access to reads as well as writes based on a number of criteria. I must be misunderstanding this statement. -Patrick ------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
