Transfer Methods. This is at the core of REST and ROA and is the foundation of Web-Oriented Architecture. You can read Roy Fielding's chapter on REST (he conceived of the approach originally) or you can just follow the simple guidelines here. At other times, protocols like BitTorrent can be used if the requirements warrant it, but these are exceptional scenarios that I will cover at some point in the future.
Ne pas citer XMPP dans les "Transfer Methods" quelque jours après l'annonce de Google Wave, et surtout le mettre dans le schéma au niveau des Microformats fait perdre toute crédibilité à l'article.
Many web resources provide mechanisms for subscribing to changes in their content. However, this change information is only made available via a polling mechanism.
A number of people have proposed mechanisms for subscribing to updates to pages or feeds, however, a missing element of all these proposals is a subscription mechanism. Sadly, this means that every site supporting this feature will likely end up with a different implementation.
Get Pingd pour la mise à mort de la syndication... (à coups de XRDS, d'Atom et de web hooks, tout un programme)
Building an XMPP-enabled Fire Eagle application is very similar to building a traditional web-based application. In fact, the XMPP componentry is intended to complement an existing application, simplifying it and imbuing it with real-time capabilities.
Piece of cake, not really. Nice usage of oAuth-over-XMPP though