background preloader


Facebook Twitter

Real-time web. The real-time web is a set of technologies and practices that enable users to receive information as soon as it is published by its authors, rather than requiring that they or their software check a source periodically for updates.

Real-time web

Difference from real-time computing[edit] The real-time web is fundamentally different from real-time computing since there is no knowing when, or if, a response will be received. PubSubHubbub. Protocol[edit] Under PubSubHubbub, there is an ecosystem of publishers, subscribers, and hubs.[1] A subscriber first retrieves content from a HTTP resource (URL) by requesting it from the webserver.


The subscriber then inspects the contents of the response, and if it references a hub, the subscriber can subscribe to that resource's URL topic[clarify] on that hub. The subscriber needs to run a web accessible server so that hubs can directly notify it when any of its subscribed topics have updated, using a webhook mechanism. Publishers expose their content with the inclusion of hub references in the HTTP headers. What is PubSubHubbub? OStatus. In January 2012, a W3C Community Group has been opened to maintain and further develop the technology.[1] Support[edit] GNU social (formerly StatusNet)FriendicabuddycloudDuuit!


GNU SocialLoreaOpenMicroBloggerProject DanubeProject See also[edit] OpenMicroBlogging - older federated microblogging specification, to be superseded by OStatus. P2. Publish–subscribe pattern. In software architecture, publish–subscribe is a messaging pattern where senders of messages, called publishers, do not program the messages to be sent directly to specific receivers, called subscribers.

Publish–subscribe pattern

Instead, published messages are characterized into classes, without knowledge of what, if any, subscribers there may be. Similarly, subscribers express interest in one or more classes, and only receive messages that are of interest, without knowledge of what, if any, publishers there are. Pub/sub is a sibling of the message queue paradigm, and is typically one part of a larger message-oriented middleware system. Most messaging systems support both the pub/sub and message queue models in their API, e.g.

Java Message Service (JMS). This pattern provides greater network scalability and a more dynamic network topology. Message filtering[edit] In the pub/sub model, subscribers typically receive only a subset of the total messages published. Webhook. Overview[edit] Webhooks are "user-defined HTTP callbacks".[2] They are usually triggered by some event, such as pushing code to a repository[3] or a comment being posted to a blog.[4] When that event occurs the source site makes an HTTP request to the URI configured for the webhook.


Users can configure them to cause events on one site to invoke behaviour on another. The action taken may be anything. Common uses are to trigger builds with continuous integration systems[5] or to notify bug tracking systems.[6] As they use HTTP, they can be integrated into web services without adding new infrastructure.[7] However there are also ways to build a message queuing service on top of HTTP—some RESTful examples include IronMQ and RestMS. In November 2012, the originator of the concept wrote about the next evolution in his thinking, the Evented Web. Publisher - Superfeedr. Atom (standard) The name Atom applies to a pair of related Web standards.

Atom (standard)

The Atom Syndication Format is an XML language used for web feeds, while the Atom Publishing Protocol (AtomPub or APP) is a simple HTTP-based protocol for creating and updating web resources. Web feeds allow software programs to check for updates published on a website. To provide a web feed, a site owner may use specialized software (such as a content management system) that publishes a list (or "feed") of recent articles or content in a standardized, machine-readable format. The feed can then be downloaded by programs that use it, like websites that syndicate content from the feed, or by feed reader programs that allow Internet users to subscribe to feeds and view their content. A feed contains entries, which may be headlines, full-text articles, excerpts, summaries, and/or links to content on a website, along with various metadata.

The Atom format was developed as an alternative to RSS.