I think this is a great feature that some hubs can provide. In my mind, this should probably be async as well, as there may be a number of notifications or the hub may also need to do retries if a subscriber is down for a moment... etc. It probably means the publisher needs to provide a callback so that the hub can indicate when the notifications are over. We might add this to the superfeedr hosted hubs, if there is enough demand for it too.
However, I don't think this belongs to the core spec itself, as it is probably not required for all use cases. Julien On Mon, Mar 14, 2011 at 4:44 PM, Cengiz Han <[email protected]> wrote: > Callback but as I said this is not a public hub. my scenario is an > enterprise solution and internally maximum server count can be 5 or may be > less. > > I know this protocol is not designed for this. But I am just thinking about > that. > > > On Mon, Mar 14, 2011 at 5:24 PM, Jay Rossiter <[email protected]>wrote: > >> >> I'd also say "What about when there are thousands of subscribers?" >> It's not exactly feasible to have a publisher sit and wait for all of those >> deliveries. >> >> >> On 3/14/2011 3:31 PM, Charl van Niekerk wrote: >> >> On Mon, 2011-03-14 at 16:08 -0600, Cengiz Han wrote: >> >> It will just send "it's done" message. >> >> What would happen though if the hub couldn't successfully deliver to all >> the subscribers? You'll need to define all the alternate scenarios. >> >> >> >> >> -- >> >> Jay Rossiter | Software Engineer/System Administrator >> Pioneering RSS Advertising Solutions >> >> [email protected] | Phone: 503.896.6187 | Fax: 503.235.2216 >> Website: www.pheedo.com | RSS: www.pheedo.info/index.xml >> > >
<<pheedo.gif>>
