|
|
|
|
|
Purpose |
Inform the application that a previously unknown Server is now available. |
|
|
|
|
Notice |
For this event notice, the notice parameter of the AspenEvent() function receives a pointer to a ASPEN_DEFINE_SERVER_NOTICE structure.
This structure is dynamically allocated by Aspen and must be freed using the AspenFreeMemory() function after use. |
|
|
|
|
Structure |
typedef struct { ASPEN_ADDRESS address; char server_name[ASPEN_MAX_SERVER_NAME]; |
|
|
|
|
Remarks |
The first time the Aspen Library becomes aware of a Server it did not previously know about, it reports an ASPEN_DefineServerNotice event to the application.
A Server definition event is only reported once for a particular Server, even if the Aspen Library receives repeated or redundant notifications from external sources on the inter-network. If the Server subsequently becomes unavailable and then later becomes available again a new definition event will be reported.
On system that use Novell Networks, Aspen will take advantage of NetWare's Service Advertising Protocol (SAP) notification to track the availability of Aspen Servers.
When Aspen is first initialized , it will check for the existence of a file by the name of Aspen.srv in the current directory. This file may contain the name and network addresses of Aspen Servers. If so the application system will receive ASPEN_DefineServerNotice events for all Servers in this file. This method of pre-defining aspen Servers is particularly useful on a system that uses TCP/IP since there is no dynamic location service currently available. |
|
|
|
|
See Also |
|
|
|
|
|
Example |
NA |
©2006 Aspen Research Group, Ltd. All rights reserved. Terms of Use.
