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

When developing a protocol-independent client/server application, client and server must meet the following requirements:

  • The server-side of the application must be able to register its existence within, or become accessible to one or more namespaces.

  • The client application must be able to find the service within a namespace and obtain the required transport protocol and addressing information.

For those accustomed to developing TCP/IP-based applications, this may seem to involve little more than looking up a host address and then using an agreed port number. Other networking schemes however, allow the location of the service, the protocol used for the service, and other attributes to be discovered at run-time.

In This Section

Namespace Organization

Namespace Provider Architecture

Name Resolution Model

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.