#include <ncpext.h> int NWGetNCPExtensionInfo ( const char NCPExtensionName, LONG NCPExtensionID, BYTE majorVersion, BYTE minorVersion, BYTE revision, void queryData);#include <nwncpext.h> or #include <nwcalls.h>
NWCCODE N_API NWGetNCPExtensionInfo( NWCONN_HANDLE conn, nuint32 NCPExtensionID, pnstr8 NCPExtensionName, pnuint8 majorVersion, pnuint8 minorVersion, pnuint8 revision, pnuint8 queryData);
The parameters are as follows:
0 | (0x00) | SUCCESSFUL | The extension was found, and the non-null output parameters were filled. |
255 | (0xFF) | ERR_NO_ITEMS_FOUND | The extension name was not found. |
1-16 | - | - | A communications error occurred. |
0 (0x00) SUCCESSFUL The extension was found, and the non-null output parameters were filled. 255 (0xFF) ERR_NO_ITEMS_FOUND The extension name was not found. 1-16 - - A communications error occurred.
The NCPExtensionName can be any character string, up to 32 bytes plus a NULL terminator. The NCP Extension names are case sensitive and must be unique for each NCP Extension. One suggestion is to name the NCP Extension the same as your NLM. To avoid naming conflicts, you should clear your NCP Extension's name through Developer Support.
You provide the fields majorVersion, minorVersion, and revision when you call NWRegisterNCPExtension. If you are going to have different versions or revisions of the NCP Extension, the client can use these fields to verify that the extension is the correct version. If you do not want to use this information, pass NULL as the parameters.
The server side and the client side of NCP Extensions should be implemented as matched sets, meaning the client side knows what the server side is expecting and what it can return. The client side also needs to know the name of the NCP Extension.
There are some cases where NWGetNCPExtensionInfo (NLM) can return all of the information your client needs, eliminating the need to call NWSendNCPExtensionRequest or to have an NCP Extension handler. This information is placed in the client's queryData buffer, whose address is passed as a parameter to NWGetNCPExtensionInfo.
This technique can be used if the service-providing NLM is periodically updating its queryData buffer (with 32 bytes or less of information) whose address was returned to the NLM when it called NWRegisterNCPExtension. If the information you want is in the NLM's queryData buffer, you can use NWGetNCPExtensionInfo to copy the contents of the service-providing NLM's queryData buffer into your client's queryData buffer. This method is useful only if a one-way server-to-client message is sufficient.
If you are using the queryData buffer, pass NULL for the queryData parameter.
0x2222 | 23 | 17 | Get File Server Information |
0x2222 | 36 | 00 | Scan NCP Extensions |
0x2222 | 36 | 02 | Scan Loaded Extensions By Name |
0x2222 | 36 | 05 | Get NCP Extension Info |
0x2222 23 17 Get File Server Information 0x2222 36 00 Scan NCP Extensions 0x2222 36 02 Scan Loaded Extensions By Name 0x2222 36 05 Get NCP Extension Info