
####Requirements:
 * JRE 6+ 

####Sending and BUFFER_FULL
When sending messages to the server via any of the various clients (MFClient, MFMarketMaker, etc), it is
possible for the TCP buffer to fill. If this happens, your call will return a BUFFER_FULL either as the return value
or as part of an OrderIdPair out parameter. The message WILL NOT be sent.
If this happens, by default, the client will disconnect from the server. 
There is a JVM arg you can provide, detailed in this document below, where the client will remain connected. In this case
the message will not be sent to the server. Subsequent attempts to send could succeed - in which case you will 
receive an OK return value. If your receive a BUFFER_FULL again, then the message cannot be sent. 
***NOTE***: It is up to you to conflate data, retry, buffer, disconnect, etc. 


####Optional Custom JVM Args: provide via -D argument

**MFTcpSendBufferBytesHint**={int >0}
if set, the TCP send buffer size will be set to provided value, or as close as 
possible (OS dependent). If not set, the default size is used. Regardless, the size will be logged to 
standard out on socket creation.

example: MFTcpSendBufferBytesHint=8192

**MFTcpReceiveBufferBytesHint**={int >0} 
if set, the TCP receive buffer size will be set to provided value, or as 
close as possible (OS dependent). If not set, the default size is used. Regardless, the size will be logged to 
standard out on socket creation.

example: MFTcpReceiveBufferBytesHint=8192

**MFStayConnectedAfterSendBufferFull**={true | false, default false } 
if not set, or set to "false', the default behaviour is to disconnect the client if the TCP send buffer 
fills. If set to "true", the client will not disconnect. 

example: MFStayConnectedAfterSendBufferFull=true

