-
Notifications
You must be signed in to change notification settings - Fork 70
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
Cascade ReaderCardAdapter #11
Labels
Comments
This is the wrong way to do. It is solved using a new abstraction layer named "Data Transport". Reader Card Adapter now only format data for targeted reader, and data are transmitted according to the Data Transport instance (could be serial port, tcp, udp ...). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To have more flexibility, we should be able to cascade several ReaderCardAdapter (having a serial communication protocol over ethernet for example).
That also means the ReaderCardAdapter choice should be an option of the ReaderUnitConfiguration, and maybe have a new abstraction layer named ReaderCardAdapterConfiguration ?
The text was updated successfully, but these errors were encountered: