<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Oops, the remote image does have a compiler. <br>
<br>
I thought for a moment and the agency doing the encoding is likely
the agency doing the un-encoding.
MessagingSession>>performNextIncomingMessage. This leads to: <br>
<br>
send: selector withParameters: parameters to: receiver over:
aRemoteMessagingSession under: remoteExchangeID<br>
<br>
"Send the message with selector and parameters to receiver,
using session's connection, for the remote exchange with ID
remoteExchangeID."<br>
<br>
..snip..<br>
<br>
receiver <b>perform:</b> selector withArguments:
parameters.<br>
<br>
.. snip.. <br>
<br>
result := receiver <b>perform:</b> selector
withArguments: parameters.<br>
<br>
<br>
The #perform: is activating the receiver and selector specified in
the message. Everything coming across the wire is a proxy encoding
material. I guess you could specify a new class to be instantiated
and that could be how imprinting happens over the wire. <br>
<br>
Onward. <br>
<br>
Chris <br>
<br>
</body>
</html>