anchor.diff:  
   This project contains several modules:
   
  -- [I/O Stuff](#io-stuff)
  +- **I/O Stuff**
   
   An EventBus API with a local and remote implementation:
   
  -- [Local EventBus](#local-eventbus):
  -- [Remote EventBus](#remote-eventbus)
  +- **Local EventBus**
  +- **Remote EventBus**
   
   Process launching mechanisms:
   
  -- [Process Launching](#process-launching)
  -- [Java Process Launching](#java-process-launching)
  +- **Process Launching**
  +- **Java Process Launching**
   
   And a way to start a Java process which can interact with its launcher through an event bus:
   
   - [Inter Java Process Communication](#ipc)
   
  -=== <a name="io-stuff"></a> I/O Stuff
  +=== I/O Stuff
   
   __Pipe__
   
  
positive.code: event.isUserEvent();            // check if it is a user event. You might listen to system events such as eventbus.server.close, eventbus.client.connect, eventbus.client.disconnect
  ```
  
  === <a name="remote-eventbus"></a>Remote EventBus
  
  `RemoteEventBus` have the same builder options that a local `EventBus` but serves as inter-process communication through a socket. One `EventBus` acts as a server and several clients can connect to it.
  
  
negative.code: javaProcess.getJavaHome();                  // automatically resolved from java home, but you can override it in the builder
  ```
  
  === Inter Java Process Communication
  
  This builder allows you to start any main class linked to a remote `EventBus` to be able to communicate with some other processes.
  
  