Polling does not perform favorably compared to push: https://code.google.com/p/pubsubhubbub/wiki/ComparingProtocols …
@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 -
@bascule@copiousfreetime@steveklabnik@jamesgolick@veganstraightedge Kafka is a good example on that. Client keeps state. -
@no7hing@copiousfreetime@steveklabnik@jamesgolick@veganstraightedge confirm. See also; ActiveMQ queue browsers - 2 more replies
New conversation -
-
-
@bascule@steveklabnik fuck websocketsThanks. 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.