Skip to content

Conversation

OtaK
Copy link
Contributor

@OtaK OtaK commented Dec 14, 2018

Closes #5

@OtaK OtaK self-assigned this Dec 14, 2018
@OtaK
Copy link
Contributor Author

OtaK commented Dec 14, 2018

The NATS codec has been broken due to premature optimizations that actually didn't work. I'm thinking of another way to do so.

The problem being that the old way of doing things was just reading the buffer by borrowing and copying data all around, creating unreasonable slowness on some cases.

Right now it needs to be rewritten IMO since we actually need to make sure we have a correct command to parse before splitting off the buffer and consuming that split in the parser.

@OtaK OtaK force-pushed the feature/parser-optimization branch from d1e3b1c to b37751f Compare December 14, 2018 16:53
@OtaK OtaK force-pushed the feature/parser-optimization branch from b37751f to 0ec3312 Compare December 14, 2018 17:16
@OtaK OtaK added this to the v0.2.0 milestone Dec 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants