-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Add a way to packetize incoming data even in the absence of a pending ORSSerialRequest. #55
Comments
Open
armadsen
pushed a commit
that referenced
this issue
Aug 8, 2015
armadsen
added a commit
that referenced
this issue
Aug 8, 2015
…fixString:userInfo:] and associated tests.
armadsen
added a commit
that referenced
this issue
Aug 8, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
armadsen
added a commit
that referenced
this issue
Aug 10, 2015
Implemented by pull request #66. |
armadsen
added a commit
that referenced
this issue
Aug 31, 2015
armadsen
added a commit
that referenced
this issue
Aug 31, 2015
This was referenced Sep 5, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A common scenario for serial communications is a device that automatically sends packets of data periodically or in response to (real world) events, rather than as a response to some request from the computer. ORSSerialPort doesn't currently provide any help with parsing/packetizing this kind of incoming data, like it does for structured request/response scenarios.
It would be valuable to provide an API so that a user of ORSSerialPort could install a "packetizer", then be notified of incoming packets that have been validated. This could look quite similar to the existing response part of ORSSerialRequest support, including the use of a response evaluator block (could be called a "packet evaluator" block).
Some requirements for the API:
-serialPort:didReceiveData:
).I think this may warrant some refactoring of the existing request response API, so I think it should wait until the next major update (ie. 2.0).
The text was updated successfully, but these errors were encountered: