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

Allow multi-packet reads #32

Open
rowleya opened this issue Nov 14, 2016 · 0 comments
Open

Allow multi-packet reads #32

rowleya opened this issue Nov 14, 2016 · 0 comments
Milestone

Comments

@rowleya
Copy link
Member

rowleya commented Nov 14, 2016

An enhancement for SCAMP and SARK would be to allow multi-packet reads, which could speed up the extraction of data. This would work as follows:

  1. The host sends a read request where the requested data is more than 256 bytes.
  2. Instead of failing, the response is sent as a sequence of packets, each with a different sequential sequence number.
  3. If any packets are lost, the host can simply request the data again, using the sequence numbers to work out where the holes in the data are.

This allows the whole protocol to be host-controlled and should be backwards-compatible; if a host requests 256 bytes, it will arrive as a single packet. The host can use a sliding window protocol by simply keeping the last sequential sequence number received and then re-requesting any packets after an appropriate time-out.

@alan-stokes alan-stokes added the incomplete_left_for_further_release Not ready for merging label Aug 3, 2017
@alan-stokes alan-stokes added this to the 5.0.0 milestone Aug 3, 2017
@dkfellows dkfellows removed the incomplete_left_for_further_release Not ready for merging label Sep 29, 2017
@dkfellows dkfellows modified the milestones: 5.0.0, 5.1.0 Aug 12, 2019
@dkfellows dkfellows modified the milestones: 5.1.0, 6.0.0 Nov 22, 2019
@dkfellows dkfellows modified the milestones: 6.0.0, 7.0.0 Apr 12, 2021
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

3 participants