7.4 aggregated Content distribution - Pubsubhubbub | Google Groups - 0 views
-
aggregated Content distribution
-
the client model for processing a single vs. aggregated distribution might be quite a bit different
-
nervous about the whole notion of PuSH co-opting <source> for its own purposes
- ...20 more annotations...
-
provenance
-
when you copy an entry from any feed document other than that feed document whose metadata is in the entry's atom:source
-
no way to indicate from which feed document you copied the entry unless you insert some extension element
-
it *is* important to know not only the source feed but *also* where you found the entry
-
Atom spec didn't envision this use case
-
atom:source is almost, but not quite, what's needed
-
confusion is understandable
-
something like a psh:provenance element
-
most recent context
-
like atom:source
-
not aggregate at the PubSubHubbub level until you've proved that
-
(a) you have to
-
(b) multipart/related won't cut it
-
the PSHB use case *was* frequently discussed in the Atom WG
-
pretty much what FeedMesh was intended to provide
-
to show provenence, you need to add an extension element
-
war stories about multipart/related and batching
-
skeptical about ease of subscriber implementation
-
This thread is a great example of peer review
-
I'll file an issue in the bug tracker
