See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Device capability offers the client a hint of what an OBEX server can do. When devices are discovered, the transport layer builds the device capability bit field. The client uses these flags to determine which services the OBEX server supports. This flag does not necessarily mean that the server offers that service; it is merely a hint. To confirm the service, the client sends a connection request to the server. If the server does not offer the requested service, the connection fails.
By default, the following capabilities are supported:
- Push
- File Browsing
- Synchronization
For IrDA, the device capability bits tell the transport layer to attempt a connection to the OBEX:IrXfer port. If that fails, the OBEX port is tried for compatibility with other devices. The mapping of device capabilities to port names is stored in the registry so it can be extended. If a new service expects connections on a different port name, a new device capability must be defined.
For Bluetooth wireless technology, the device capability hint instructs the transport to connect to the correct service class identifier on the remote device.