<Jan> If the words above make others feel like "poor souls", too I should propably take the responsibility - it was me who said that, not Mark :-) </Jan>
My apologies for that incorrect attribution. It is getting a bit hard to follow the conversation thread. And no.. You did not make me feel bad, just amused. The amusement comes from trying to reconcile the disconnect between the often touted refrain that REST is a principle that is based on the very simple concepts which underpin the web, with the claim that in order to reach understanding of this particular nirvana, one needs to have an deep and multi-layered understanding of some rather complex distributed computing technologies. To my mind at least, REST does not have a Horsey-Ducky story i.e. A good enough and simple enough description of how, what, when and who that you can use to explain to someone that takes them from Point A to Point B RE: Understanding. <Jan> Besides: I hear no WS-* proponents claim WS-* would do better than REST[1]. Thus, if we know no better way, why not evangelize it? </Jan> I am a WS-* user, not an evangelist. But I've been in the game long enough to know that every solution has its pros and cons. As such I would never make the claim that WS-* is "better" than REST. I am very interested in learning about REST because I truly want to understand what the trade-offs are. So I continue to avidly follow this discussion in the hopes that I will reach that level of understanding. I am not there yet. <Jan> I recall Gregg as (sort of) advocating Jini over both, WS-* and REST </Jan> There no "sort of" with Gregg and Jini :-) But his advocacy has made me curious enough to pick up a book on Jini to explore the technology because there are some particular use cases where a SOA implemented using Jini may indeed be viable. But to borrow a phrase from Steve, there is a degree of "formalism" around Jini that allows me to wrap my head around it. I am still trying to obtain that clarity around REST. Regards, - Anil :- :- Anil John :- http://www.aniltj.com/blog :-
