While the Jess function (socket) is a nice convenience, read/readline and printout provide only text io (as opposed to binary), and they may not be sufficient for a sturdy application.
There is no particular wizardry involved with writing a set of userfunctions that wrap the essentials from java.net. This will also enable you to provide the inescapable error handling, retries, etc. Also, consider that read/readline and printout are inclined to block, so you may have to control threading, which is also somewhat easier if done in Java. Wolfgang ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Matt Hutchinson Sent: Mittwoch, 17. Dezember 2008 19:29 To: [email protected] Subject: JESS: JESS socket and router Hi everyone, I've done some Googling and had a look at the JESS manual, but does anyone have anymore info or sample code for: (socket <Internet-hostname> <TCP-port-number> <router-identifier>) My goal is to have a remote piece of software tracking what's going on in the other software running on a separate machine.... Thanks, Matt -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [email protected]' in the BODY of a message to [email protected], NOT to the list (use your own address!) List problems? Notify [email protected]. --------------------------------------------------------------------
