On 02/26/2011 11:51 PM, Jeff Lindsay wrote:
Perhaps what is needed is to split off, or start a new project that is
solely dedicated to the "push something" idea, and then PSHB can remain the
"push feeds" projects but defers all the push tech itself to the other
project. (or start a new feeds project, I don't think it maters which)
Yeah, I think the camp observation resonates with me. As far as
forking, I figure the PSHB spec could either be simplified for the
general case with an addon for feeds, or PSHB can continue to be about
feeds and contain a subset spec used by the PS camp. Either way, there
are common issues that overlap.
Although as currently written the two issues are intertwined in the
spec, the feed-specific parts are actually not difficult to separate
from the rest:
Fundamentally, PubSubHubbub provides a way to subscribe to changes to a
resource. There are many ways that the "changeset" can be represented.
As an accident of history, an representation for Atom and RSS feeds was
defined first, and the simpler "just send the entire resource"
representation was not defined until later.
However, I think all it takes is to reorganize the specification a
little so that the default case is whole-resource updates and then some
specialized, resource-type-specific representations and a mechanism for
determining which is desired by the client. I don't see any reason to do
anything radical like fork off another spec that would only be slightly
different than what we have today in terms of protocol flow.
