@raggi you "like" pipelining, right?. If you have any time, would appreciate your thoughts on https://github.com/celluloid/reel/pull/73 …
@raggi you may be able to put it into that state quite easily right now. It should probably raise an exception
-
-
@bascule ofc. the hard problem is, if you started processing anything already, then you have to back that out. 2 doesn't help here either -
@raggi I think if the response generator does something like that it should spit out a 500 for that response then continue as usual -
@bascule you may have to abort the lot, depending if you're dealing with idempotents or not (because SHOULDs), or define behavior >.< -
@raggi failing fast on the whole connection is definitely the "let it fail" way to do it ;) -
@bascule i raised in RFI, but was ignored -
@raggi :( let it fail might be nice because it keeps the semantics simple: just blow up -
@bascule i should probably send notes to peon, but it's already too late more than likely
End of conversation
New conversation -
-
-
@bascule that said, client specific resource queues can be implemented in 2, if UAs only open one socketThanks. 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.