I need some help understanding the spec in regards to "fat pings" (or
what I think is a fat ping, anyway).

Section 4 of the Core Draft #3 states:
"The Publisher makes the decision as to include full body, truncated
body, or meta data of most recent event(s). One of:

URL + metadata
URL + metadata + truncated
URL + metadata + full"

with the last option being the content that is new. However, there has
been some concern lately
(http://groups.google.com/group/pubsubhubbub/browse_thread/thread/a5a516521ed64cf9)
about the lack of fat pings and the rest of the spec seems to gloss
over this decision that could be made by the publisher.

So, is it just standard (in practice?) that the publisher isn't likely
to push full content in a notification? And instead they are willing
to deal with the thundering hurd? Guess I'm just looking for some
clarity on this part of the spec - seems like it is a possibility
according to Sec 4, but as stated, the rest of the spec doesn't
mention much about publishers/hubs dealing with this scenario.

Thanks!

andy

Reply via email to