Lists Home |
Date Index |
> - It's not going to scale if I'm the only consumer of a "feed." A bank
> isn't going to appreciate having all their customers ping them every
> few minutes to see if anything changed, and Bloglines won't help unless
> there are lots of people subscribing to a given feed.
I have been trying to think about this a lot. Not much good I suppose-- for
a while I tried to think out the concept of a new protocol. A reverse HTTP,
and opt-in push type of mechanism where the publisher maintains a list of
subscribers and pushes the data to listeners running on the client machines.
This, of course, has many problems-- addressability, trust, who controls the
opt-in system (to repel the spammers), to name a few. All of these are
solvable-- addressability with p2p, trust with certificates, control through
trust-- but it is sloppy and not using what is already built out. Because of
this I went back to "subscription"-- we use it to describe feeds but I think
it is a misnomer. What we really have is HTTP automation scripts
masquerading as subscription services. If that's all, then why not just
insert a middle-man that can be repeatedly pinged and let the bank push the
data to the middle-man? Oh yeah. That's how POP works. That's what we are
trying to get away from.