Agreed on proving need first.  I have some war stories about
multipart/related and batching that may be relevant; I'm skeptical
about ease of subscriber implementation.

On Saturday, October 24, 2009, Tim Bray <[email protected]> wrote:
>
> On Sat, Oct 24, 2009 at 9:45 AM, John Panzer <[email protected]> wrote:
>
>> The right thing to do IMHO is to add something like a psh:provenance element
>> that is just like atom:source but tracks the most recent context of the
>> entry.
>
> The right thing to do IMHO is not aggregate at the PubSubHubbub level
> until you've proved that (a) you have to and (b) multipart/related
> won't cut it.
>
>  -T
>

-- 
--
John Panzer / Google
[email protected] / abstractioneer.org / @jpanzer

Reply via email to