> Anyway the point is that all Web services specifications are designed for use > over multiple communications protocols. So HTTP specific stuff is ruled out > by definition.
That's not true, Eric. Supporting multiple protocols does not necessarily mean treating them all the same (as if they were transports). It can also mean supporting each one where it makes sense. That, right there, is how the industry got itself into this mess. The former approach fights an uphill battle against millions of deployed software components (servers, firewalls, caches), while the latter works *with* that infrastructure. This fight was over before it began. Mark. ------------------------ Yahoo! Groups Sponsor --------------------~--> Great things are happening at Yahoo! Groups. See the new email design. http://us.click.yahoo.com/TISQkA/hOaOAA/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/
