On 3/14/2010 6:24 PM, Brett Slatkin wrote:
> This is a proposal for a firehose feed. How would it work for track
> and geo queries? Couldn't this be more generic?
I assumed that those would be passed as parameters as an alternate to a
standard topic URL.
PuSH is a decent model for firehose delivery, but even though the data may
be delivered via RSS/Atom, it's not truly a feed in the standard sense of the
word. This is really an extension on the base PuSH design. This is a special
use case, with special requirements and, frequently, special authentication
considerations, so I don't think that it should be forced into the standard
subscription model. These endpoints aren't (or at least shouldn't be in the
vast majority of cases, IMO) used via transparent auto-discovery. It would
lead to users subscribing to data that they don't want or need, putting the
bigger burden on the source.
> Not sure about this assertion.
I'll move this to a separate thread, so as not to muddle the discussions.
--
Jay Rossiter | Software Engineer/System Administrator
Pioneering RSS Advertising Solutions
[email protected] <mailto:[email protected]> | Phone: 503.896.6187 |
Fax: 503.235.2216
Website: www.pheedo.com <http://www.pheedo.com/> | RSS:
www.pheedo.info/index.xml <http://www.pheedo.info/index.xml>
