Intermec CV30 Intermec Terminal Emulator (ITE) Programmer's Reference Manual - Page 167

ITE Implementation

View all Intermec CV30 manuals Add to My Manuals Save this manual to your list of manuals

• 
  1
• 
  2
• 
  3
• 
  4
• 
  5
• 
  6
• 
  7
• 
  8
• 
  9
• 
  10
• 
  11
• 
  12
• 
  13
• 
  14
• 
  15
• 
  16
• 
  17
• 
  18
• 
  19
• 
  20
• 
  21
• 
  22
• 
  23
• 
  24
• 
  25
• 
  26
• 
  27
• 
  28
• 
  29
• 
  30
• 
  31
• 
  32
• 
  33
• 
  34
• 
  35
• 
  36
• 
  37
• 
  38
• 
  39
• 
  40
• 
  41
• 
  42
• 
  43
• 
  44
• 
  45
• 
  46
• 
  47
• 
  48
• 
  49
• 
  50
• 
  51
• 
  52
• 
  53
• 
  54
• 
  55
• 
  56
• 
  57
• 
  58
• 
  59
• 
  60
• 
  61
• 
  62
• 
  63
• 
  64
• 
  65
• 
  66
• 
  67
• 
  68
• 
  69
• 
  70
• 
  71
• 
  72
• 
  73
• 
  74
• 
  75
• 
  76
• 
  77
• 
  78
• 
  79
• 
  80
• 
  81
• 
  82
• 
  83
• 
  84
• 
  85
• 
  86
• 
  87
• 
  88
• 
  89
• 
  90
• 
  91
• 
  92
• 
  93
• 
  94
• 
  95
• 
  96
• 
  97
• 
  98
• 
  99
• 
  100
• 
  101
• 
  102
• 
  103
• 
  104
• 
  105
• 
  106
• 
  107
• 
  108
• 
  109
• 
  110
• 
  111
• 
  112
• 
  113
• 
  114
• 
  115
• 
  116
• 
  117
• 
  118
• 
  119
• 
  120
• 
  121
• 
  122
• 
  123
• 
  124
• 
  125
• 
  126
• 
  127
• 
  128
• 
  129
• 
  130
• 
  131
• 
  132
• 
  133
• 
  134
• 
  135
• 
  136
• 
  137
• 
  138
• 
  139
• 
  140
• 
  141
• 
  142
• 
  143
• 
  144
• 
  145
• 
  146
• 
  147
• 
  148
• 
  149
• 
  150
• 
  151
• 
  152
• 
  153
• 
  154
• 
  155
• 
  156
• 
  157
• 
  158
• 
  159
• 
  160
• 
  161
• 
  162
• 
  163
• 
  164
• 
  165
• 
  166
• 
  167
• 
  168
• 
  169
• 
  170
• 
  171
• 
  172
• 
  173
• 
  174
• 
  175
• 
  176
• 
  177
• 
  178
• 
  179
• 
  180
• 
  181
• 
  182
• 
  183
• 
  184

Match case Limit results 1 per page

---

100% Actual Size Fit Width Fit Height Fit Page Automatic

Appendix B — About RPC Implementation

Intermec Terminal Emulator (ITE) Programmer’s Reference Manual

155

else

std::cout << "Error calling 'Sum'\n\n";

ITE Implementation

The following section describes each of the functions implemented for ITE RPC.

The functions are described using logical parameters. These are packed into XML by

XMLRPC. The actual format of the calls are dependent on the XMLRPC

implementation chosen (see above). However, the XML itself will be the same no

matter the implementation.

ITE RPC XML API supports the following functions.

ITC.registerScreenContentsCallBack()

This function tells ITE the IP address for callback for returning the screen contents.

This function takes three parameters:

•

Name of the function to callback with the screen contents. Always set to

ITC.GetScreenContents

.

•

IP address of the client that is attaching to the ITE application.

•

Port to use to communicate between the ITE application and the attached client.

This function increments the count of attached clients and then sends the message

WM_ATTACHED_CLIENTS with the wparam set to the current count of attached

clients. This function also calls invalidate rect on the ITE handle, which sends a

WM_PAINT message to the ITE application so the client can get the current screen

contents.

Example:

class GetScreenContents : public XmlRpc::XmlRpcServerMethod

{

public:GetScreenContents(XmlRpc::XmlRpcServer* s) :

XmlRpc::XmlRpcServerMethod("ITC.GetScreenContents", s) {}

void execute(XmlRpc::XmlRpcValue& params, XmlRpc::XmlRpcValue& result)

{

try

{

int nArgs = params.size();

int type = params.getType();

std::string& structString = params.toXml();

screenParams.clear();

for(int i = 0; i < nArgs; i++)

Note

: XmlRpcValue is a template library (generic) that defines many

operators for the types defined in the XMLRPC specification (

http://

www.xmlrpc.com

).

Note

:

The exact calling sequence is implementation-specific. If you chose a

different implementation of XMLRPC, you will have to abide by how it

codes the calls rather than the example above. For instance, see the C#

implementation in

http://www.xml-rpc.net

.