Confirmed users
118
edits
WebAPI/WebNFC: Difference between revisions
→NDEF Utilitiy function for parsing / constructing NDEF records
| Line 225: | Line 225: | ||
MozNDEFRecord follows the NFC Forum format, and NfcUtils in {{bug|963556}} will provide some basic constants and utility functions to create and parse NDEF records. | MozNDEFRecord follows the NFC Forum format, and NfcUtils in {{bug|963556}} will provide some basic constants and utility functions to create and parse NDEF records. | ||
NfcUtil offers a set of utility functions to handle NDEF messages according to NFCForum-TS-NDEF_1.0. It exports the following functions: | |||
- parseNDEF: parse an NDEF message | |||
- parseHandoverNDEF: parse a NDEF message that represents a handover request | |||
or a handover select message | |||
- searchForBluetoothAC: search for a Bluetooth Alternate Carrier in a | |||
handover NDEF message | |||
- parseBluetoothSSP: Parses a Carrier Data Record that contains a | |||
Bluetooth Secure Simple Pairing record | |||
- encodeHandoverRequest: returns a NDEF message that contains a handover | |||
request message | |||
- encodeHandoverSelect: returns a NDEF message that contains a handover | |||
select message | |||
== NDEF Connect Example == | == NDEF Connect Example == | ||