Re: The deep difference between request/response and fire-and-forget

>I'm strongly against standardizing any MEP that can't be deployed on
>HTTP.  That would be very very strange to standardize an MEP and not
>standardize any bindings for that MEP.  It doesn't pass the giggle test
>at all..
>  
>
That doesn't pass /my/ giggle test.  Do what now?  HTTP is the only
protocol in the world?  Standardize a one-way MEP, bind it to XMPP
<message/> and I promise I won't giggle a bit.