On 06/08/2010 10:29 AM, Monica Keller wrote:
I believe the proposal at http://code.google.com/p/pubsubhubbub/wiki/ArbitraryContentTypes is fairly generic but does not prevent hubs to produce something more advanced. If we put into the spec that the hub must retransmit the response from publisher verbatim we are making it harder for them to provide additional services and its less RESTful
The PubSubHubbub protocol has two "sides": publisher to hub, and hub to subscriber.
There's no reason why you can't just implement one "side" of this, and do something custom on the other side, if you have unique needs that the baseline protocol doesn't provide for. Several implementations already use subsets of hubbub in some situations, and that's fine.
I'm not sure what you mean by it being "less RESTful" to have the hub treat the payload as opaque.
