The second way is on the client side who explicitly creates the ChaosSocket. When created the ChaosSocket will call it super class constructor which will do the initial communication with the server. After the connection to the server has been created the ChaosSocket reads in 720 bytes. These bytes contain the synchronization data needed to sync the master and slave systems. The socket will create the Lorenz and RK objects and use the data read in to sync them up to the server s system.
Results Here are the results of how the program worked.
The first thing was to see how sensitive the constants in the Lorenz system are to change. The ides is to see how accurate each constant has to be before the message can be understood. If the slave side is off one any one of these parameters by the amount specified Java throws an exception stating that the data is not in UTF format. One decimal place below these points Java will either throw the exception or the string will be shown with some of the characters incorrect. The message on a whole though is recognizable and readable.