This is a legacy Whisperer Classic API version that should not be used for new development. 

This API version will be formally deprecated by the end of 2019.


Requirements: Java 6+

Changelog

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.

[3.13.0-600] - Oct 17 2018

  • [ADDED] - 2 optional JVM args to control socket behavior:
    • MFTcpReceiveBufferBytesHint {>0} - if provided, will try to set the TCP Receive buffer size to the value.
      The actual value set is OS dependent but will in practice be close to the set value. The actual used value will be logged whenever a socket is created.
    • MFTcpSendBufferBytesHint {>0} - if provided, will try to set the TCP Send buffer size to the value.
      The actual value set is OS dependent but will in practice be close to the set value. The actual used value will be logged whenever a socket is created.
  • [ADDED] - Potential minor-breaking change to latency calculations. PingTime timestamps generated at the client-side are now nano precision using System.nanoTime. This means they are no longer comparable to the server timestamp. The advantage is you can measure the round-trip latency in nanoseconds. If you were using the milliseconds ping times in calculations this will likely break your usage. The reason for this change is clients are close to or sub 1 ms for server to client latency and the nano precision is required.

[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