-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Highly optimize Varint21FrameDecoder #3792
base: master
Are you sure you want to change the base?
Conversation
Removed byte[] alloc and reduce loops by using ByteBuf.forEachByte only ones and than parsing the Varint with bitshifting from the buffer
can we also remove the direct IO buffers info? |
That is extremly disrespectfull i have written the code myself it took me about a hour |
Simply assuming that the code is copied and asking for the license from the rightful owner is disrespectful in my opinion. |
Also if it wasn‘t disrespectful why delete it |
This comment was marked as off-topic.
This comment was marked as off-topic.
I actually don't know what "friend circle" you mean and what "skills" i do miss, anyways this inappropriate on github. It seems like you have a personal issue with me, or somebody i know. If so you got my discord tag, we can talk about it in private |
Keep it friendly guys. By the way is it possible to add some security checks to the decoder with this patch? |
what do you mean by security checks |
And if it's not the skills, it's your lack of veracity. |
Some limiters for example, so it can't be bypassed by some naughty users. |
I dont understand what can be bypassed here, and i dont know what you mean by limits, its a Varint21FrameDecoder, the limit is in the name of the decoder |
Removed byte[] alloc and reduce loops by using ByteBuf.forEachByte only ones and than parsing the Varint with bitshifting from the buffer