To test multiple Pool *scripts* (rather than compiled executables),
in multiple instances of Scite, you may have to edit 
SciteGlobal.Properties or SciteUser.Properties, and add/change the line: 

check.if.already.open=0

and then restart Scite. If you have associated .au3 files with
"Edit upon open" rather than "Run upon open", you can then
double-click each .au3 in turn to open it in its own Scite window.


For testing CLNtest on a single machine, you'll need to run
1 copy of PostOffice_Solo
2 or more copies of CLNtest

For testing CLNmaster + CLNslave on a single machine, you'll need to run
1 copy of PostOffice_Solo
1 copy of CLNmaster
1 copy of CLNslave



If you want to test on a (W)LAN, replace all instances of
PostOffice_Solo with PostOffice_Client
EXCEPT one machine, which HAS to run
PostOffice_Server

In this case, you should ensure that the Server is fully initialised
before starting the first PostOffice_Client.

A PostOffice_Client that does not find its Server upon startup will start
scanning the entire subnet, so then it might take a few minutes before
it connects. A server that does not find any clients connecting within
the defined timeout will redefine itself as client, and start looking
for a different Server.

See also the LAN section in the Remarks in Pool.au3, as well as 
the various _TIMEOUT variables related to networking.

On a LAN, you may achieve much better, reliable throughput than on a WLAN, 
in which case network-related multimsg delays can be reduced accordingly.


You can preset a Server IP for PostOffice_Clients to use by editing the
local PostOffice_<class>.ini file. When you start up the Server, its
current Ip is displayed in the GUI's title bar (NB GUI is visible ONLY
when running from Scite, NOT when running PostOffice as executable)


Have fun playing in the Pool,
RTFC, 20 April 2015.