sorry, haven't quite got something I can readily publish
-
-
Replying to @edefic @yoshuawuyts
a good chunk of this is just stuff that's been brewing in my head for a long time and hasn't really been written down
2 replies 0 retweets 1 like -
Replying to @edefic @yoshuawuyts
canonical error codes are a must (https://godoc.org/google.golang.org/grpc/codes …), (recursive) deadlines+explicit cancellation are a must for QoS
1 reply 0 retweets 1 like -
Replying to @edefic @yoshuawuyts
being able to change the names of things without changing encoding (compactness is a bonus, but decoupling matters more)
1 reply 0 retweets 1 like -
Replying to @edefic @yoshuawuyts
duplex streaming is unmissable, though I'd like the ability to switch to a raw byte stream instead of message-based
1 reply 0 retweets 0 likes -
Replying to @edefic @yoshuawuyts
for things like storage services, mainly, and encapsulating arbitrary byte streams — just regular HTTP/2, basically
1 reply 0 retweets 0 likes -
Replying to @edefic @FrozenFire
ahhh, yeah I see what you mean - that would def be nice
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @FrozenFire
fwiw your 'messages' can be byte chunks rather than proto
1 reply 0 retweets 0 likes -
Replying to @louiscryan
example? Or do you mean simply ignoring pbuf and using TCP / HTTP2 directly instead?
@FrozenFire2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts @FrozenFire
should be able to do same in other langs.
1 reply 0 retweets 0 likes
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.