Expand description
MAP protocol logic — commands, folder navigation, MNS server, and iOS quirks.
Modules§
- client
- MAP client — OBEX session setup, SETPATH sequencing, and request dispatch.
- folders
- Folder listing and SETPATH navigation for MAP folder hierarchy.
- messages
- Message listing, retrieval, push, and status operations (
GetMessage,PushMessage,SetMessageStatus). - mns_
event - MAP-event-report event types and the parser that decodes them from the phone’s MNS PUT body.
- mns_
server - MNS OBEX server — accepts connections from the remote device and yields MAP event reports.
- params
- MAP application parameter tag constants, bitflags, and encoder functions.
- quirks
- iOS-specific OBEX/MAP quirks that deviate from the Bluetooth specification.
- xml
- MAP XML parser for message listings (
MAP-msg-listing).
Structs§
- BMessage
- Single-level BENV structure; nested BENV not supported.
- Folder
Entry - A single MAP folder from a
GetFolderListingresponse. - Folder
Listing - Parsed body of a MAP
GetFolderListingOBEX response.
Enums§
- BMessage
Error - bMessage parse errors — missing required fields, unrecognised STATUS/TYPE values, and unterminated sections.
- MapError
- MAP client/MNS errors — OBEX, transport, server response, parse, input validation, and encoding.
- Message
Status - Read/unread status from the bMessage STATUS field.
- Message
Type - Message type from the bMessage TYPE field.
- Obex
Error - OBEX client errors — connection state, packet codec, server rejection, and missing protocol headers.
- Transport
Error - OBEX framing errors — invalid length, unexpected EOF, and external transport failures.
- XmlError
- MAP XML parsing errors — quick-xml parse, attribute decode, and folder name UTF-8 validation.