Feature #3681

A "push" form of the protocol

Added by Lars Marius Garshol almost 6 years ago. Updated over 5 years ago.

Status:New Start date:2010-10-07
Priority:Normal Due date:
Assignee:Graham Moore % Done:

0%

Category:-
Target version:-

Description

In many cases, the recipient of fragments cannot make connections to the producer, because of security restrictions such as firewalls. In these cases, a push form of the protocol would be desirable. It might use the Atom Publishing Protocol, or it might use something much simpler.

History

Updated by Lars Heuer over 5 years ago

Having read <http://www.garshol.priv.no/blog/215.html> I assume that PubSubHubbub does not work for your use case, since you're talking about a different push than I thought you're talking about.
PubSubHubbub can inform subscribers (clients) via POST about updates, and servers inform hubs about updates via POST. So servers push updates to hubs and hubs push updates to clients.

You're talking about uploading fragments/snapshots to severs which is a completely different thing.

Updated by Lars Heuer over 5 years ago

You're talking about uploading fragments/snapshots to severs which is a completely different thing.

Well, actually it is not "completely" different, since servers could subscribe to hubs and could fetch fragments/snapshots from other servers, but you want something more simple. A client POSTs a fragment to a server. The server saves and publishes it.

Also available in: Atom PDF