It screams the protocol should've used protobuf in 2.0
-
-
-
I know about HPACK, but I'm not sure I like the trade-offs, compared to just dumping protobuf coding of everything. And that even if HPACK is faster due to memory bandwidth. Vastly harder to implement than proto IMO.
-
I’m not convinced protobuf would help me in this situation. For this use case I think I may be able to do fixed position parsing.
-
No, but it would help because there wouldn't be half a billion ways to write "OK, and I have no content" where half of them are accepted by half the clients and half are not. Text parsing should just die in hell IMO.
-
Okay but I’m writing a closed system that can be tweaked entirely for performance reasons. I’m basically just using HTTP because there’s no better socket servers and protocols along with benchmarking tools available.
End of conversation
New conversation -
-
-
Kelly you're supposed to slow down and get larger as you get older. Stop making the rest of us look bad.
-
HTTP/1.1 411
End of conversation
New conversation -
-
-
Next step - reduce response to "HTTP/1.1 204\r\n\r\n"
-
Read my follow up tweets. I did that :P
-
Too lazy to read entire conversation, but have motivation to write a reply. What's wrong with my energy management? :)
End of conversation
New conversation -
-
-
Happy to help with your drag racing hobby
:)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.