Keeping one's host/port information secret from other users can be achieved by starting a master server local to a secure physical or virtual Intranet.
For users behind a firewall, this might actually be the only way to try out these operations as the default master server might be unreachable.
To start your own master server type in a window something like:
?- master_server('my.secure.local.computer',7788)=>run_master_server.
Use a fact
master_server('my.secure.local.computer',7788).
Type in or have your code execute:
set_master_server('my.secure.local.computer',7788)
in both your client and server programs intended to be managed by your own master server.
A useful application to this is to build a local chat line not seen by users from the outside.
Progressively, commercial quality security will be built in BinProlog, especially if nonsensical export restrictions in US and Canada will be removed on strong cryptography.
To keep the workload of the master server minimal, only when an error is detected by a client, the master_server is asked to refresh its information and possibly remove dead servers from its database.