L_InetSendCmd

#include "l_bitmap.h"
#include "ltnet.h"

L_INT EXT_FUNCTION L_InetSendCmd(hComputer, uCommand, uCommandID, hPacket)

L_COMP hComputer;	/* handle to a remote computer */
CMDTYPE uCommand;	/* command type */
L_UINT uCommandID;	/* command id */
HINETPACK hPacket;	/* handle to the packet object */

Sends a command to a remote computer.

Parameter	Description
hComputer	Handle to the remote computer to which the command will be sent.
uCommand	The command to send. For a list of possible values, refer to CMDTYPE.
uCommandID	Command ID. Each command sent by a member of a connection should have a unique ID. Since a member of a connection may send several commands, this ID allows that member to identify when a specific command request has been completed.
hPacket	Handle to an INET packet object containing the parameters for the command. You can pass NULL if the command doesn’t need any parameters.

Returns

SUCCESS	This function was successful.
< 1	An occurred. Refer to Return Codes.

Comments

The remote computer should respond by calling L_InetSendRsp in its INETCOMMANDCALLBACK function. This callback function must be set using L_InetSetCommandCallback.

To receive responses to commands, provide an INETRESPONSECALLBACK function. This function must be set using L_InetSetResponseCallback.

Some commands will send back only the command’s status (indicating whether the command succeeded or not). But some commands will send back additional information if the command succeeds. For example, responses to L_InetSendLoadCmd will send the bitmap ID while responses to L_InetSendCreateWinCmd will send the window identifier (which can be used to resize or close the window).

Required DLLs and Libraries

LTNET

For a listing of the exact DLLs and Libraries needed, based on the toolkit version, refer to Files To Be Included With Your Application

Funtions:	L_InetSendRsp, INETCOMMANDCALLBACK, INETRESPONSECALLBACK, L_InetSetCommandCallback
Topics:	Sending Commands and Responses
	A Client-Server Diagram: Sending Commands and Responses