Polling does not perform favorably compared to push: https://code.google.com/p/pubsubhubbub/wiki/ComparingProtocols …
-
-
@bascule@steveklabnik yea except that websockets are a huge pain in the ass in practice and aren't worth it for lots of circumstances -
@jamesgolick@steveklabnik this was actually in an SOA talk... had nothing to do with websockets -
@bascule@jamesgolick I helped@veganstraightedge develop that talk ;) -
@steveklabnik@jamesgolick@veganstraightedge haha awesome. My reaction to the whole thing is a bit o_O. Interesting to see others' SOA tho -
@bascule@jamesgolick@veganstraightedge you're right about overhead and latency, but there are other architectural flaws in a push model -
@steveklabnik@bascule@jamesgolick@veganstraightedge for instance, recovery when the receiver is down and wants to get missing data. -
@copiousfreetime@steveklabnik@jamesgolick@veganstraightedge recipient should ask the pusher for everything since the last thing it saw - 4 more replies
New conversation -
-
-
@bascule well, push requires more state than polling in that it must remember the subscribers and must verify subscriptions.@steveklabnik -
@wilkieii@steveklabnik nobody ever said push was easier ;) -
@bascule haha. my instinct is to object to anybody who does not properly define "overhead" in a generalization :)@steveklabnik
End of conversation
New conversation -
-
-
@bascule it is *certainly* lower latency until the point you have to replicate. which is kinda the motivation for PuSH.@steveklabnikThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@steveklabnik Some of our customers have been able to cut by 95% their polling just because they get the data pushed.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.