Adobe 38039927 Extended User Guide - Page 262

ADOBE FIREWORKS CS3 258 Extending Guide Fireworks RPC transactions pass XML between an RPC client and the Fireworks RPC server built in to Fireworks. The RPC client is any supported program that connects to Fireworks through a TCP stream on port 12124. The Fireworks RPC server is the internal code that listens on TCP port 12124 and then handles client requests. During the RPC transaction, information flows from client to server: Note: The RPC client is not required to disconnect after each XML request. The RPC client can keep the connection open and send additional XML requests (the TCP resubmission timeout is 30 seconds). However, only one XML request can be outstanding at a time. In other words, the RPC client cannot send a second request until it receives a reply to the first request, because there is no queueing mechanism to hold pending requests. RPC client XML requests The XML request contains the following four pieces of information for Fireworks: • The type of operation to perform • The name of the operation to perform • The object on which the operation is performed • Any parameters the operation needs Note: XML requests are specially formatted XML document fragments, not full XML documents. XML requests are sent to the server in UTF-8 encoding and terminated with the null (0) character. Logically, requests contain two parts: the envelope and the parameters. The envelope specifies the requested operation (for instance, get or set) and the object that the operation is performed on. The parameters (strings, integers, arrays, and so on) specify how the operation happens. The envelope tag contains the parameter tag, as follows: The RPC client sends the following four types of requests, specified in the XML tag name of the envelope: