Hi pekr, > > This is the mode in which async code was executed by ARexx on old Amiga. > > That's nice, excempt, imo, above scenario looses capability of getting thru > firewall, because of custom = non 80 port Rugby is supposed to connect back to. > Anyone?
Client port could be 80, the message arriving has an unique ID created by user and copied by server to mark the answer message (on Amiga ports was free - only memory limited them - in TCP they have a limit, perhaps it should be better to use ID instead of port number). To think the message like an object, it could be: message: make object [ adress: 123.24.35.5 portnum: 80 id: 1234 ;integer or issue body: [] ] ---- Ciao Romano -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
