Merge lp:~andrefcruz/nfcpy/npp-1.0 into lp:nfcpy
Proposed by
André Cruz
Status: | Merged |
---|---|
Merged at revision: | 78 |
Proposed branch: | lp:~andrefcruz/nfcpy/npp-1.0 |
Merge into: | lp:nfcpy |
Diff against target: |
103 lines (+23/-13) 1 file modified
nfc/npp/server.py (+23/-13) |
To merge this branch: | bzr merge lp:~andrefcruz/nfcpy/npp-1.0 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stephen Tiedemann | Approve | ||
Review via email: mp+64703@code.launchpad.net |
Description of the change
I implemented the ability for the NPP server to run in single-threaded mode and be stopped by the return of the process() method.
In my scenario this is useful because I only want to receive a message, process it, and continue the program without the NPP server (the Android API only allows the phone to send 1 message per LLCP link establishment).
If you find this useful then merge...
To post a comment you must log in.
Andre, I wouldn't mind to make the NPP server single- threaded/ single- connection *onyly*. As implemented in Android, it is always *one* system client that opens *one* connection to send NDEF data, An NPP server should actually never need to handle more than one connection at a time (in practice not even during the same session). And I don't think there will be much evolution of the NPP specification; I rather dare to predict a forthcoming Android release will support the NFC Forum way of getting NDEF across LLCP.