ncadg_ipx attribute
The ncadg_ipx keyword identifies IPX as the protocol family for the endpoint. This protocol family is obsolete and should not be used in new applications.
endpoint("ncadg_ipx:link-address[port-name]")
Parameters
-
link-address
-
Specifies the host server. This may be either a character string (the server name), or a 20-digit hexadecimal number that consists of the host server's network address (8 digits) concatenated with the node address (12 digits). See Remarks for instructions on how to obtain the network address and node address. A NULL string specifies the local computer.
-
port-name
-
Specifies an optional 16-bit number that represents the socket address. Values can range from 1 to 65535. When no value is specified, the endpoint-mapping service selects a valid port-name value.
Remarks
The following restrictions apply to the datagram protocols, ncadg_ipx and ncadg_ip_udp:
- They do not support callbacks. Any functions using the [callback] attribute will fail.
- They do not support use of the pipe type constructor.
When using the ncadg_ipx transport, the server name is exactly the same as the 32-bit Windows server name. However, since the names are distributed using Novell protocols, they must conform to the Novell naming conventions. If a server name is not a valid Novell name, servers will not be able to create endpoints with the ncadg_ipx transport. The following is a partial list of characters prohibited in Novell server names:
" * + . / : ; < = > ? [ ] \ |
The ncadg_ipx transport is supported by the version of NWLink supplied with MS Client 3.0.
16-bit Windows client applications that use the ncadg_ipx transport require that the file Nwipxspx.dll be installed in order to run under the WOW subsystem. Contact Novell to obtain this file.
To obtain the network and node addresses, use Novell's comcheck utility, or the Novell-defined API IPXGetInternetAddress. On Windows, you can also obtain these addresses with the ipxroute config command.
The syntax of the TCP/IP transport port string, like all port strings, is defined independently of the IDL specification. The compiler performs some syntax checking but does not guarantee that the endpoint specification is correct. Some errors may be reported at run time rather than at compile time.
Note
This protocol family is not supported in Windows XP.
Examples
[
uuid(12345678-4000-2006-0000-20000000001a),
version(1.1),
endpoint("ncadg_ipx:[1000]")
]
interface iface
{
// Interface definition statements.
}
See also