UFT/1 -vs- UFT/2 
 
Implementors should be prepared to identify UFT/1 servers, 
which are in production at some sites.   A UFT/1 server will 
answer the connect with a 1xx herald,  where a UFT/2 server 
would send a 2xx herald.   So what?   Well UFT/1 didn't allow 
for the 3xx "send more data" response after a DATA command, 
so the client must not expect it.   (UFT/1 servers also do not 
know about AUXDATA or META commands) 
 
UNIQUE NUMBERS 
 
The response code numbers are unique.   That is,  for any 
particular response from the server,  the code sent can be 
used in a table lookup for national language equivalent text 
on the client end. 
 
	rnn pp pp pp ... ; text in server's native language 
 
The first digit  (here "r")  identifies the range,  which corresponds 
to ACK, NAK, etc.   The following digits  (two at this time)  map to 
a unique message which the client may replace.   Following that is a 
list of positional parameters which the message translator in the 
client may use with its own translation of the message.   Following 
that,  separated by a semi-colon is the message in the server's 
native tongue. 
 

