On 06/07/2010 06:44 PM, Monica Keller wrote:
I would like it to be very easy to consume arbitrary formats. The question is how much should the hub should normalize the response from the publisher to help the subscribers ? Is it a dumb rebroadcaster which maintains fidelity of the publisher's response or is it a smarter agent which validates before re syndicating ?
Given that the hubbub architecture has a coupling between the hub and publisher, it's left to the publisher to choose a hub that suits the publisher's needs.
I think the baseline generic implementation such as on app engine should aspire to be as generic as possible so that it doesn't need to be altered for each new application requirement, and this is what the specification should describe. You can't really be "smart" and generic at the same time.
However, a publisher is free to choose a hub that provides additional value-add services such as normalization, if the normalization that the hub does makes sense for the payload the publisher offers.
