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.
A version of this page is also available for
4/8/2010

This method notifies the user of incoming requests.

Syntax 

HRESULT Notify(
  OBEX_EVENT 
Event,
  IUnknown* 
pUnk1,
  IUnknown* 
pUnk2
);

Parameters

Event

[in] Event message. The possible values of this parameter are identified in the following table.

Value Description

OE_DEVICE_ARRIVAL

A new device is within range.

OE_DEVICE_DEPARTURE

A device that was in range is no longer within range.

OE_DEVICE_UPDATE

The name of a remote device has changed.
pUnk1

[in] Pointer to the first parameter definition.

pUnk2

[in] Pointer to the second parameter definition.

Return Value

The appropriate HResult is returned.

Remarks

This method is useful when an event requires the user's attention ( Disconnectand Abortrequests, for example). The user can also be prompted for a password when making a connection to an OBEX server. The parameter definitions that are passed to the function are dependent upon the message.

This method is called when a device is discovered or when more information about it is found.

When you implement this method, it must be thread safe.

Note:
There is one callback thread for each IObexinterface. No time consuming operations should be performed on the callback notifications. If any long operations are performed, then notification of the other OBEX events will be delayed until the notification returns.

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

500 Internal Server Error

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.