@bascule @steveklabnik yea except that websockets are a huge pain in the ass in practice and aren't worth it for lots of circumstances
-
-
Replying to @jamesgolick
@jamesgolick@steveklabnik this was actually in an SOA talk... had nothing to do with websockets2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@jamesgolick I helped@veganstraightedge develop that talk ;)1 reply 0 retweets 0 likes -
Replying to @steveklabnik
@steveklabnik@jamesgolick@veganstraightedge haha awesome. My reaction to the whole thing is a bit o_O. Interesting to see others' SOA tho2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@jamesgolick@veganstraightedge you're right about overhead and latency, but there are other architectural flaws in a push model1 reply 0 retweets 1 like -
Replying to @steveklabnik
@steveklabnik@bascule@jamesgolick@veganstraightedge for instance, recovery when the receiver is down and wants to get missing data.2 replies 0 retweets 0 likes -
Replying to @copiousfreetime
@copiousfreetime@steveklabnik@jamesgolick@veganstraightedge recipient should ask the pusher for everything since the last thing it saw2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@copiousfreetime@steveklabnik@jamesgolick@veganstraightedge Kafka is a good example on that. Client keeps state.1 reply 0 retweets 0 likes -
Replying to @no7hing
@no7hing@copiousfreetime@steveklabnik@jamesgolick@veganstraightedge confirm. See also; ActiveMQ queue browsers1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@no7hing@copiousfreetime@steveklabnik@veganstraightedge why are you guys still cc'ing me on this thread?1 reply 0 retweets 0 likes
@jamesgolick @no7hing @copiousfreetime @steveklabnik @veganstraightedge Twitter conversation entropy
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.