tag:blogger.com,1999:blog-13639021.post4352518958349203674..comments2024-03-05T04:05:47.416-08:00Comments on The Wisdom of Ganesh: Why Is REST (Seen To Be) Simpler Than SOAP-Based Web Services?prasadgchttp://www.blogger.com/profile/00179696156998026173noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13639021.post-1763351801411271482007-12-13T09:43:00.000-08:002007-12-13T09:43:00.000-08:00See Tango demos at:http://blogs.sun.com/arungupta/...See Tango demos at:<BR/><BR/>http://blogs.sun.com/arungupta/entry/excel_using_wsit_javaone_2007<BR/>http://blogs.sun.com/arungupta/entry/screncast_ws7_secure_and_reliableArun Guptahttps://www.blogger.com/profile/16061355511504961025noreply@blogger.comtag:blogger.com,1999:blog-13639021.post-58151865815294207322007-12-13T04:50:00.000-08:002007-12-13T04:50:00.000-08:00Agreed on the "horses for courses" approach with S...Agreed on the "horses for courses" approach with SOAP vs. REST. <BR/><BR/>However I am not in agreement with you in regards to concluding that REST will become just as complex as SOAP.<BR/><BR/>The basic premise of REST lies in the simplicity and atomicity of its approach. If someone creates a complicated Resource Oriented Architecture (ROA) then they are missing the point and frankly, using the wrong approach. <BR/><BR/>SOAP-Messaging is where you need to go if you see your architecture evolving into complicated message exchanges with multi-boundary contexts and a need for consistency.<BR/><BR/>Just my two cents...<BR/><BR/>Cheers,<BR/><BR/>Zubin.Zubin Wadiahttps://www.blogger.com/profile/03547079212723029279noreply@blogger.com