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.

Sign up for GitHub

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

Jump to bottom

Bi-directional protocol and serverbound API #28

Open
aramperes opened this issue Aug 1, 2021 · 1 comment
Open

Bi-directional protocol and serverbound API #28

aramperes opened this issue Aug 1, 2021 · 1 comment
Assignees
@aramperes
Labels
enhancement New feature or request
Milestone
1.0.0

Comments

@aramperes
Copy link
Owner

Right now the network implementation and API are entirely client-sided. In order to re-implement server-side components (#26) and implement unit testing (#2), the network stack should support crafting packets for both directions.

The public API needs to be reworked a bit to support this.
@aramperes aramperes added the enhancement New feature or request label Aug 1, 2021
@aramperes aramperes added this to the 1.0.0 milestone Aug 1, 2021
aramperes added a commit that referenced this issue Aug 3, 2021
@aramperes
Start work on generic protocol impl for #28
2224c1d
@aramperes aramperes self-assigned this Aug 3, 2021
aramperes added a commit that referenced this issue Aug 4, 2021
@aramperes
Start work on generic protocol impl for #28 (#29)
1e3481e
@aramperes
Copy link
Owner Author

Bi-directional parsing is now implemented under the rups::proto module (#29)

@aramperes aramperes mentioned this issue Aug 4, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aramperes aramperes

Labels
enhancement New feature or request
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@aramperes