Skip to content

Feature/tuple frames #614

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

Merged
merged 1 commit into from
Apr 15, 2019
Merged

Feature/tuple frames #614

merged 1 commit into from
Apr 15, 2019

Conversation

OlegDokuka
Copy link
Member

This PR provides TupleXByteBuf as a replacement for CompositByteBuf

@OlegDokuka OlegDokuka requested a review from robertroeser April 9, 2019 14:25
@OlegDokuka OlegDokuka force-pushed the feature/tupleFrames branch 2 times, most recently from d81d15f to a3763b1 Compare April 15, 2019 08:52
@OlegDokuka OlegDokuka force-pushed the feature/tupleFrames branch from a3763b1 to c82e305 Compare April 15, 2019 08:58
@robertroeser robertroeser merged commit 102590e into develop Apr 15, 2019
@robertroeser robertroeser deleted the feature/tupleFrames branch April 15, 2019 17:52
OlegDokuka added a commit that referenced this pull request May 29, 2019
robertroeser pushed a commit that referenced this pull request Jun 6, 2019
* backports fixes bug with incorrect WS framesize setup (#614)

* rollback mockito version

* changed timeout

* changed timeout

* small fix

* replace with concurrent maps

Signed-off-by: Oleh Dokuka <[email protected]>
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