h*      0.3.0 Safe-Inferred"distributed-process-simplelocalnetGiven a hostname and a port number, initialize the multicast system.Note: it is important that you never send messages larger than the maximum message size; if you do, all subsequent communication will probably fail.Returns a reader and a writer.NOTE: By rights the two functions should be "locally" polymorphic in a), but this requires impredicative types."distributed-process-simplelocalnet Multicast IP"distributed-process-simplelocalnet Port number"distributed-process-simplelocalnetMaximum message size Safe-Inferred "distributed-process-simplelocalnetMessages to slave nodesThis datatype is not exposed; instead, we expose primitives for dealing with slaves."distributed-process-simplelocalnet Local backend"distributed-process-simplelocalnetCreate a new local node"distributed-process-simplelocalnet findPeers t broadcasts a  who's there?& message on the local network, waits t microseconds, and then collects and returns the answers. You can use this to dynamically discover peer nodes."distributed-process-simplelocalnetMake sure that all log messages are printed by the logger on the current node"distributed-process-simplelocalnetInitialize the backend"distributed-process-simplelocalnetCreate a new local node"distributed-process-simplelocalnetPeer discovery"distributed-process-simplelocalnet6Respond to peer discovery requests sent by other nodes"distributed-process-simplelocalnetMake sure that all log messages are printed by the logger on this node"distributed-process-simplelocalnetCalling slave sets up a new local node and then waits. You start processes on the slave by calling spawn from other nodes.This function does not return. The only way to exit the slave is to CTRL-C the process or call terminateSlave from another node."distributed-process-simplelocalnet The slave controller interprets s"distributed-process-simplelocalnet(Terminate the slave at the given node ID "distributed-process-simplelocalnetFind slave nodes "distributed-process-simplelocalnetTerminate all slaves "distributed-process-simplelocalnet  finds all slaves  currently available on the local network, redirects all log messages to itself, and then calls the specified process, passing the list of slaves nodes.Terminates when the specified process terminates. If you want to terminate the slaves when the master terminates, you should manually call  .If you start more slave nodes after having started the master node, you can discover them with later calls to  +, but be aware that you will need to call redirectLogHere+ to redirect their logs to the master node.'Note that you can use functionality of SimpleLocalnet directly (through ), instead of using  , if the master2slave distinction does not suit your application."distributed-process-simplelocalnetshut down the logger process. This ensures that any pending messages are flushed before the process exits.        ?distributed-process-simplelocalnet-0.3.0-CD9JolJtWRU3WAe4E8aUV7Control.Distributed.Process.Backend.SimpleLocalnet.Internal.Multicast2Control.Distributed.Process.Backend.SimpleLocalnet"distributed-process-simplelocalnet initMulticastBackend newLocalNode findPeersredirectLogsHereinitializeBackend startSlaveterminateSlave findSlavesterminateAllSlaves startMaster$fBinaryPeerDiscoveryMsg$fBinarySlaveControllerMsg$fBinaryRedirectLogsReply$fShowRedirectLogsReply$fShowSlaveControllerMsgSlaveControllerMsgapiNewLocalNode apiFindPeerspeerDiscoveryDaemonapiRedirectLogsHereslaveControllershutdownLogger