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. |
This interface exposes the name and address of the device. The address is transport-specific but presented as a string.
The following table shows the methods of this interface.
| Method | Description |
|---|---|
|
Sends an Abortrequest to the server. |
|
|
Connects to the specified device. |
|
|
Disconnects the current connection. |
|
|
Returns a standard COM IPropertyBagor IPropertyBag2interface that describes the device. |
|
|
Issues a Getcommand for an object on an OBEX server. |
|
|
Issues a Putcommand for an object that is passed to the server. |
|
|
Sets the password for requests. |
|
|
Issues a SetPathcommand to the server. |
Remarks
All OBEX transactions have an associated header that contains information pertaining to device type and identification.
Requirements
| Header | obex.h, obex.idl |
| Library | uuid.lib |
| Windows Embedded CE | Windows CE .NET 4.0 and later |
| Windows Mobile | Pocket PC 2002 and later, Smartphone 2002 and later |
See Also
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.