Integer responseID without nonBlocking support #53
Conversation
There was a problem hiding this comment.
We lose non-blocking, transmit return value, and transmit exceptions? I'd rather not lose the functionality, especially non-blocking.
|
Well I told you I have deleted it cause I wont use it and you asked a pull request so here it is. Later i might limit the integer and add nonblocking back.What I am thinking about is a fixed size ConcurrentHashMap which blocks when it is full and can be used for fixing this unexpected behavior even with using byte for responseID. |
|
Aye, sorry I should have mentioned that I'd rather not remove features unless there is good reason. Your PR is still useful for the other bits. If you'd like to add back the functionality and keep your other changes great, if not the PR can stay until myself or someone else gets to doing it. Not sure we'd want to block if no responseIDs are available. Using byte for responseID isn't terribly important, using a varint is fine if it is needed. A separate, single byte could be used for various flags (eg exceptions) instead of cramming them into the responseID. |
2 participants
No description provided.