Communication between separate JADE environments

[ConvertFromOldNGs]

by Robert Barr >> Fri, 5 Nov 1999 3:27:16 GMT

Pragmatists will appreciate that, if tx volumes are sufficiently low and data relationships are simple, then implementing option 1 (shared file) is v. easy and (with a small pinch of forethought) robust. KISS wherever possible.

(CardSchema now provides a facility that notifies JADE of (registered) file system changes, making periodic file monitoring unnecessary).

Rob

[ConvertFromOldNGs]

by Robert Barr >> Fri, 5 Nov 1999 3:38:10 GMT

With regards to option 2), I've used http successfully a few times now
to provide (low volume) data transfer between JADE systems - coding is easy, especially if transfer is half-duplex and the 'server' already has http capability configured. Advantages over straight tcp messages are additional integrity and SSL authentication and encryption, which can be important if the systems are physically remote.

(CardSchema provides simple http client services).

Rob