James Snell wrote:
> For XMPP-enabled environments, draft-saintandre-atompub-notify-01
> is Goodness. Not every environment is going to be XMPP-enabled.
> Just about everyone is HTTP POST enabled.
I think that focusing on the differences between XMPP and HTTP POST
is not really useful in this discussion. Each transport protocol has
advantages in one or another environment. What's interesting is not the
transport protocol but rather the payload that is transported! (i.e. The
slogan "It's about the Entries, Stupid!" applies in this case.)
I think the important point is that there probably isn't a great
deal of justification for having different payload formats for these
protocols. If we strip away the XMPP and HTTP "transport" wrappers,
overhead, etc. I don't see any reason why it would be useful to have
different messages.
bob wyman
