Skip to content
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

CBitStream Buffers #9

Open
Ragora opened this issue Aug 17, 2015 · 0 comments
Open

CBitStream Buffers #9

Ragora opened this issue Aug 17, 2015 · 0 comments

Comments

@Ragora
Copy link
Member

Ragora commented Aug 17, 2015

Currently, CBitStream instances are created and destructed a lot within the scope of the netcode. In the scope of unpacking incoming messages, a single CBitStream object should be kept around and merely reset for each packet to unpack while also being instructed as to where its next unpacking target resides.

Further, when messages are sent at any time, a new CBitStream is constructed which entails not only memory allocation for the CBitStream itself but also the heap entry for its working data. These especially should be reused in the same way as they would be for incoming messages.

@Ragora Ragora added this to the Engine Maintenance milestone Aug 17, 2015
@Ragora Ragora changed the title BitStream Buffers CBitStream Buffers Aug 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant