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

Use Control EP for socket commands #19

Closed
dberliner opened this issue Sep 6, 2019 · 0 comments · Fixed by #20
Closed

Use Control EP for socket commands #19

dberliner opened this issue Sep 6, 2019 · 0 comments · Fixed by #20
Assignees

Comments

@dberliner
Copy link
Collaborator

Device will have to manage synchronization to make sure we don't close before data is sent and similar problems. But we should move towards the more standard procedure of using a control endpoint to communicate these short (preferable low latency) commands. Rather than stacking every command into a bulk transfer, the bulk EP will become exclusively for handling write operations between the device and host.

Instead of using variable length payload packets for commands like CONNECT, use fixed size command packets up to 64-bytes long. Dispense with the immediate type and make all bulk transfers payload.

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 a pull request may close this issue.

1 participant