All notable changes to 3.13.0 Java API will be documented in this file.
The 'name' of the api is 3.13.0 and will never change.
Changes will always be backwards compatible.
[3.13.0-510] - May 30 2018
[ADDED] - Exposed CancelOrder method where client provides the cancelId, orderId, and clOrdId in both zerogc and regular MFClients.
[3.13.0-506] - Dec 20 2017
[FIXED] - ZeroGC MFClient now implement #getPingTimes. If useHeartbeats is set to true (by default it is), the the client will periodically send a message the server and the server will respond. The timestamps of these messages are stored and available to the user.
[3.13.0-505] - Dec 6 2016
[FIXED] threading issue with MFClient
[3.13.0-504] - Sept 13 2016
[FIXED] issue with the OrderIDMap and order modification.
[3.13.0-503] - June 1 2016
[FIXED] issue in zerogc MFClient with re-use of a SubmitOrderMessage
[3.13.0-502] - Apr 14 2016
[FIXED] issue with zerogc where large EventReports overrun default MFString size
[3.13.0-501] - Mar 3 2016
[FIXED] a json comma missing issue for zerogc MFClient
[3.13.0-500] - Jan 26 2016
[ADDED] Change for zerogc MFClient to properly catch and log any message decode error
[3.13.0-400] - Dec 14 2015
[ADDED] Normalization of api and zerogc directories and corresponding package names
[3.13.0-300] - Dec 14 2015
[ADDED] Fix issue with zerogc sample trading application - regarding the OrderIdPair
[3.13.0-202] - Nov 11 2015
[FIXED] issue in the MFClient where there was no comma added to the quoteID JSON structure when more than one parameter was passed in
[3.13.0-201] - Aug 6 2015
[FIXED] issue with duplicate orders where MFClient does not recognize the original order
[3.13.0-200] - May 28 2015
[ADDED] getBatch methods to zerogc java client
[3.13.0-100] - May 21 2015
[ADDED] Simplify reconnect logic to always resubscribe on reconnects