tag:blogger.com,1999:blog-439652399294426401.post8880738985009825686..comments2008-09-05T08:30:41.707+05:30Sanjiva Weerawaranahttp://www.blogger.com/profile/10278760563625840210noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-439652399294426401.post-45035044718237877252008-09-05T08:30:00.000+05:302008-09-05T08:30:00.000+05:30Come on Tim you of course know that MTOM was after having done SOAP with Attachments (SwA) .. and this is exactly the same as SwA except for Atom - AwA :). That's a perfectly fine path to take - and in case you didn't know, there were very good reasons to go to MTOM: basically to be able to sign and secure the message as a single entity, even if it had attachments. <BR/><BR/>@asbjornu: MTOM was not a reinvention of MIME (and if you want to find a reinvention then point to DIME) - it was a mechanism invented to make it possible to secure an entire message as a single thing. <BR/><BR/>If Atom ever has a feed signing thing then the problem will hit Atom too. <BR/><BR/>Anyway, Tim, I'll buy you a beer (in Sri Lanka if you'd like to visit!) if in 2 years from now we're not looking at a bunch more REST-* specs :).Sanjiva Weerawaranahttp://www.blogger.com/profile/10278760563625840210noreply@blogger.comtag:blogger.com,1999:blog-439652399294426401.post-81662735229853363972008-09-04T17:42:00.000+05:302008-09-04T17:42:00.000+05:30Tim's right. MTOM tries to reinvent existing standards (like MIME) with an XML-based syntax. As if being XML wins us anything. That's what WS-* is all about, really. Reinventing existing technology, only wrapping everything in angle brackets. Plus serving those angle brackets in the least optimal way through a pseudo neutral transport protocol (which always is HTTP). How is that better?asbjornuhttp://www.blogger.com/profile/11117147483795790759noreply@blogger.comtag:blogger.com,1999:blog-439652399294426401.post-10024435526947665512008-09-04T02:44:00.000+05:302008-09-04T02:44:00.000+05:30Heh, I'll take that page-count bet.<BR/><BR/>As regards re-inventing it all, it's possible this shows the importance of process; if the WS-* project had had an an IETF-like ultra-transparent process, the outcome might have been better. But we'll never know.<BR/><BR/>BTW, this isn't like MTOM at all, I don't think. MTOM tries to stretch an XML Infoset over your MIME package, while Joe's proposal just says "Send two things at once, use standard multipart packaging, and here's how you deal with them."Timhttp://www.blogger.com/profile/02509044056955394983noreply@blogger.com