On Sun, Mar 14, 2010 at 1:17 PM, Brett Slatkin <[email protected]> wrote:
> 1. Use XRD
>
ick
2. Link relation in the feed itself
>
not bad ("easy"), but superfluous 99.9% of the time; in-efficient.
> 3. Verification request includes discovery information
>
ick. in-congruent overloading of verification process.
4. Fuck it
>
this would get annoying.
5. Like #1 except skip XRD and use a new mode
>
just as icky as #1.
if we're not already... let's keep in mind that there firehoses are not
*just* the complete blast of data for a given service (e.g. twitter-hose...
"all of twitter's data"). you may want more granular hoses based on some
other defined grouping of messages. for example, I'm using some group-ware
message boarding app and I want the "hose" of all the posts for that group
to be available and discoverable. this scenario needs some
spec'ing/definition/common-understanding of how to advertise availability
and discovery in order to get it right. "Fucking it" will leave a mess on
this front, while I think it would actually work for the "firehoses" at the
meta level (e.g. FB, Twitter.... "the big guys").
continued in Jay's thread...
Jud
