The hub is designated by the publisher in the feed themselves... So its 1. Not sure I understand Alexis comment...
Sent from my iPhone On Jul 23, 2010, at 11:16, Alexis Richardson <[email protected]> wrote: > I think (1) is an important use case that we should look into. > > It will require a written proposal, since it is not currently covered.. > > alexis > > > On Fri, Jul 23, 2010 at 4:51 PM, Cole <[email protected]> wrote: >> Which of the following will cause a Hub to record a new subscription >> and consider itself to be managing it: >> >> 1. A publisher pings a hub for a topic URL (even if not Subscribers >> are currently subscribed to that particular topic URL). The topic feed >> includes the particularly pinged hub as a valid hub. >> >> 2. A subscriber attempts to subscribe to a new feed and it is marked >> as a new subscription in the hub. I understand that the hub can be a >> distributer for arbitrary feeds, even if they don't list the hub as a >> distributor and it will poll the feeds and push to its subscribers. >> >> Where does the initial data come from? We are looking to expose a lot >> of data through a rest interface and updated through pubsubhubbub. >> Does the initial data population occur outside of the pubsubhubbub >> chain? How does that work with the initial step shown in the >> slideshow? When the subscriber first attempts to connect to the >> publisher they are "forwarded" to the hub. Does this mean redirected? >> If that is the case, does the first connection to the hub cause the >> hub to give the subscriber ALL of the content of that particular feed?
