Files
externals/linux/doc/Onixs.CME.4.8.0/html/NewFeatures_8md_source.html

82 lines
18 KiB
HTML

<!-- HTML header for doxygen 1.8.11-->
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.11"/>
<title>OnixS C++ CME Market Data Handler: Pages/NewFeatures.md Source File</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
<link href="onixs-doxygen.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript">
$(window).scroll(function() {
if ($(this).scrollTop() > 1)
{
$('header').addClass("sticky");
}
else
{
$('header').removeClass("sticky");
}
});
</script>
</head>
<body>
<header>
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td id="projectlogo"><a href="http://www.onixs.biz"><img alt="Logo" src="onixs.svg"/></a></td>
<td style="padding-left: 0.5em;">
<div id="projectname">OnixS C++ CME Market Data Handler
&#160;<span id="projectnumber">4.8.0.10</span>
</div>
<div id="projectbrief">API documentation</div>
</td>
</tr>
</tbody>
</table>
</div>
</header>
<div id="wrapper">
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<!-- end header part -->
<!-- Generated by Doxygen 1.8.11 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Home</span></a></li>
<li><a href="modules.html"><span>Contents</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li class="current"><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
<div id="navrow2" class="tabs2">
<ul class="tablist">
<li><a href="files.html"><span>File&#160;List</span></a></li>
<li><a href="globals.html"><span>File&#160;Members</span></a></li>
</ul>
</div>
</div><!-- top -->
<div class="header">
<div class="headertitle">
<div class="title">Pages/NewFeatures.md</div> </div>
</div><!--header-->
<div class="contents">
<a href="NewFeatures_8md.html">Go to the documentation of this file.</a><div class="fragment"><div class="line"><a name="l00001"></a><span class="lineno"> 1</span>&#160;\addtogroup new-features</div><div class="line"><a name="l00002"></a><span class="lineno"> 2</span>&#160;</div><div class="line"><a name="l00003"></a><span class="lineno"> 3</span>&#160;\brief Summaries major features and improvements of given release. </div><div class="line"><a name="l00004"></a><span class="lineno"> 4</span>&#160;</div><div class="line"><a name="l00005"></a><span class="lineno"> 5</span>&#160;\section new-messaging-api The New Messaging Subsystem</div><div class="line"><a name="l00006"></a><span class="lineno"> 6</span>&#160;</div><div class="line"><a name="l00007"></a><span class="lineno"> 7</span>&#160;The messaging subsystem has been redesigned in the SDK. Previously, </div><div class="line"><a name="l00008"></a><span class="lineno"> 8</span>&#160;a message was representing a FIX container that provided access to </div><div class="line"><a name="l00009"></a><span class="lineno"> 9</span>&#160;the field values using tags as keys. Also, the processing machinery </div><div class="line"><a name="l00010"></a><span class="lineno"> 10</span>&#160;used generic SBE (Simple Binary Encoding) decoder to extract data from </div><div class="line"><a name="l00011"></a><span class="lineno"> 11</span>&#160;the SBE-encoded content transmitted by CME MDP and to build a FIX message. </div><div class="line"><a name="l00012"></a><span class="lineno"> 12</span>&#160;</div><div class="line"><a name="l00013"></a><span class="lineno"> 13</span>&#160;The given approach of manipulating market data provided certain benefit </div><div class="line"><a name="l00014"></a><span class="lineno"> 14</span>&#160;as it allowed to work with all market data through a unified FIX container. </div><div class="line"><a name="l00015"></a><span class="lineno"> 15</span>&#160;The drawback of the given approach was latency. SBE-encoded content had to </div><div class="line"><a name="l00016"></a><span class="lineno"> 16</span>&#160;decoded and copied to the FIX container on a processing layer. </div><div class="line"><a name="l00017"></a><span class="lineno"> 17</span>&#160;</div><div class="line"><a name="l00018"></a><span class="lineno"> 18</span>&#160;The messaging subsystem has been redesigned to provide customers </div><div class="line"><a name="l00019"></a><span class="lineno"> 19</span>&#160;with maximal performance, and now the API exposes classes for each </div><div class="line"><a name="l00020"></a><span class="lineno"> 20</span>&#160;type of SBE message defined by SBE coding templates. </div><div class="line"><a name="l00021"></a><span class="lineno"> 21</span>&#160;</div><div class="line"><a name="l00022"></a><span class="lineno"> 22</span>&#160;The given approach allows the customers to be much closer to the </div><div class="line"><a name="l00023"></a><span class="lineno"> 23</span>&#160;original data transmitted by CME, as the SBE to FIX mapping is rather </div><div class="line"><a name="l00024"></a><span class="lineno"> 24</span>&#160;semantical and thus losses certain important characteristics which </div><div class="line"><a name="l00025"></a><span class="lineno"> 25</span>&#160;the customers may require. </div><div class="line"><a name="l00026"></a><span class="lineno"> 26</span>&#160;</div><div class="line"><a name="l00027"></a><span class="lineno"> 27</span>&#160;Also, the performance is dramatically improved due to eliminating SBE </div><div class="line"><a name="l00028"></a><span class="lineno"> 28</span>&#160;to FIX transformation subsystem, and now data is directly accessed without </div><div class="line"><a name="l00029"></a><span class="lineno"> 29</span>&#160;any intermediate copying. </div><div class="line"><a name="l00030"></a><span class="lineno"> 30</span>&#160;</div><div class="line"><a name="l00031"></a><span class="lineno"> 31</span>&#160;\section new-listeners New Events And Listeners</div><div class="line"><a name="l00032"></a><span class="lineno"> 32</span>&#160;</div><div class="line"><a name="l00033"></a><span class="lineno"> 33</span>&#160;Events and listeners, reflecting miscellaneous aspects </div><div class="line"><a name="l00034"></a><span class="lineno"> 34</span>&#160;of the Handler behavior, have been redesigned, and now </div><div class="line"><a name="l00035"></a><span class="lineno"> 35</span>&#160;are more consistent compare to the previous design. </div><div class="line"><a name="l00036"></a><span class="lineno"> 36</span>&#160;</div><div class="line"><a name="l00037"></a><span class="lineno"> 37</span>&#160;The table below represents a quick overview of major </div><div class="line"><a name="l00038"></a><span class="lineno"> 38</span>&#160;listeners and key improvements.</div><div class="line"><a name="l00039"></a><span class="lineno"> 39</span>&#160;</div><div class="line"><a name="l00040"></a><span class="lineno"> 40</span>&#160;&lt;table&gt;</div><div class="line"><a name="l00041"></a><span class="lineno"> 41</span>&#160; &lt;tr&gt;</div><div class="line"><a name="l00042"></a><span class="lineno"> 42</span>&#160; &lt;th&gt;Listener&lt;/th&gt;</div><div class="line"><a name="l00043"></a><span class="lineno"> 43</span>&#160; &lt;th&gt;Description&lt;/th&gt;</div><div class="line"><a name="l00044"></a><span class="lineno"> 44</span>&#160; &lt;/tr&gt;</div><div class="line"><a name="l00045"></a><span class="lineno"> 45</span>&#160; &lt;tr&gt;</div><div class="line"><a name="l00046"></a><span class="lineno"> 46</span>&#160; &lt;td&gt;OnixS::CME::MDH::HandlerListener&lt;/td&gt;</div><div class="line"><a name="l00047"></a><span class="lineno"> 47</span>&#160; &lt;td&gt;</div><div class="line"><a name="l00048"></a><span class="lineno"> 48</span>&#160; Encapsulates Handler events. </div><div class="line"><a name="l00049"></a><span class="lineno"> 49</span>&#160; </div><div class="line"><a name="l00050"></a><span class="lineno"> 50</span>&#160; Previously, the Handler behavior-related events were spread </div><div class="line"><a name="l00051"></a><span class="lineno"> 51</span>&#160; in a few listeners like a listener for the Handler state and </div><div class="line"><a name="l00052"></a><span class="lineno"> 52</span>&#160; issues (warning, error). Now, everything is gathered into a </div><div class="line"><a name="l00053"></a><span class="lineno"> 53</span>&#160; single listener. The states have been substituted with the </div><div class="line"><a name="l00054"></a><span class="lineno"> 54</span>&#160; correspondent callbacks and enhanced. </div><div class="line"><a name="l00055"></a><span class="lineno"> 55</span>&#160;</div><div class="line"><a name="l00056"></a><span class="lineno"> 56</span>&#160; For example, now the callback identifying the end of recovery </div><div class="line"><a name="l00057"></a><span class="lineno"> 57</span>&#160; exposes the status of recovery completion indicating whether </div><div class="line"><a name="l00058"></a><span class="lineno"> 58</span>&#160; the recovery is succeeded or failed with a detailed description </div><div class="line"><a name="l00059"></a><span class="lineno"> 59</span>&#160; of the last case. </div><div class="line"><a name="l00060"></a><span class="lineno"> 60</span>&#160; &lt;/td&gt;</div><div class="line"><a name="l00061"></a><span class="lineno"> 61</span>&#160; &lt;/tr&gt;</div><div class="line"><a name="l00062"></a><span class="lineno"> 62</span>&#160; &lt;tr&gt;</div><div class="line"><a name="l00063"></a><span class="lineno"> 63</span>&#160; &lt;td&gt;OnixS::CME::MDH::MarketDataListener&lt;/td&gt;</div><div class="line"><a name="l00064"></a><span class="lineno"> 64</span>&#160; &lt;td&gt;</div><div class="line"><a name="l00065"></a><span class="lineno"> 65</span>&#160; Encapsulates market data events. </div><div class="line"><a name="l00066"></a><span class="lineno"> 66</span>&#160; </div><div class="line"><a name="l00067"></a><span class="lineno"> 67</span>&#160; The given listener is a close analog to the </div><div class="line"><a name="l00068"></a><span class="lineno"> 68</span>&#160; OnixS::CME::MDP3::MessageProcessingListener exposed </div><div class="line"><a name="l00069"></a><span class="lineno"> 69</span>&#160; by the previous generations of the SDK. However, it was </div><div class="line"><a name="l00070"></a><span class="lineno"> 70</span>&#160; enhanced with packet-related events exposing original </div><div class="line"><a name="l00071"></a><span class="lineno"> 71</span>&#160; data received by Handler instances. </div><div class="line"><a name="l00072"></a><span class="lineno"> 72</span>&#160; &lt;/td&gt;</div><div class="line"><a name="l00073"></a><span class="lineno"> 73</span>&#160; &lt;/tr&gt;</div><div class="line"><a name="l00074"></a><span class="lineno"> 74</span>&#160; &lt;tr&gt;</div><div class="line"><a name="l00075"></a><span class="lineno"> 75</span>&#160; &lt;td&gt;OnixS::CME::MDH::SecurityListener&lt;/td&gt;</div><div class="line"><a name="l00076"></a><span class="lineno"> 76</span>&#160; &lt;td&gt;</div><div class="line"><a name="l00077"></a><span class="lineno"> 77</span>&#160; Encapsulates security-related events. </div><div class="line"><a name="l00078"></a><span class="lineno"> 78</span>&#160; </div><div class="line"><a name="l00079"></a><span class="lineno"> 79</span>&#160; Previously, security-related events were raised through </div><div class="line"><a name="l00080"></a><span class="lineno"> 80</span>&#160; a number of listeners like the OnixS::CME::MDP3::TradeListener </div><div class="line"><a name="l00081"></a><span class="lineno"> 81</span>&#160; and the OnixS::CME::MDP3::DirectChangeBookLister. </div><div class="line"><a name="l00082"></a><span class="lineno"> 82</span>&#160; &lt;/td&gt;</div><div class="line"><a name="l00083"></a><span class="lineno"> 83</span>&#160; &lt;/tr&gt;</div><div class="line"><a name="l00084"></a><span class="lineno"> 84</span>&#160;&lt;/table&gt;</div><div class="line"><a name="l00085"></a><span class="lineno"> 85</span>&#160;</div><div class="line"><a name="l00086"></a><span class="lineno"> 86</span>&#160;\section new-session-settings Market Data Processing (Session) Settings</div><div class="line"><a name="l00087"></a><span class="lineno"> 87</span>&#160;</div><div class="line"><a name="l00088"></a><span class="lineno"> 88</span>&#160;Previously, the way how Handler processed market data was defined by which </div><div class="line"><a name="l00089"></a><span class="lineno"> 89</span>&#160;overload of the OnixS::CME::MDH::Handler::start member was used to spawning </div><div class="line"><a name="l00090"></a><span class="lineno"> 90</span>&#160;processing. </div><div class="line"><a name="l00091"></a><span class="lineno"> 91</span>&#160;</div><div class="line"><a name="l00092"></a><span class="lineno"> 92</span>&#160;Starting with version 4 of the SDK, the OnixS::CME::MDH::SessionSettings </div><div class="line"><a name="l00093"></a><span class="lineno"> 93</span>&#160;class was invented to define market data processing for the session. Settings </div><div class="line"><a name="l00094"></a><span class="lineno"> 94</span>&#160;are supplied to the OnixS::CME::MDH::Handler::start member as a parameter. </div><div class="line"><a name="l00095"></a><span class="lineno"> 95</span>&#160;Currently, settings allow defining whether market data recovery must be done </div><div class="line"><a name="l00096"></a><span class="lineno"> 96</span>&#160;at the beginning of market data processing or in case of data loss or other </div><div class="line"><a name="l00097"></a><span class="lineno"> 97</span>&#160;processing error and so on. Also, settings allow defining which type of market </div><div class="line"><a name="l00098"></a><span class="lineno"> 98</span>&#160;(by price or by order or both) is to be recovered. New parameters offer a wider </div><div class="line"><a name="l00099"></a><span class="lineno"> 99</span>&#160;variety of processing ways compare to previous versions. </div><div class="line"><a name="l00100"></a><span class="lineno"> 100</span>&#160;</div><div class="line"><a name="l00101"></a><span class="lineno"> 101</span>&#160;\section tcp-recovery-with-natural-refresh Using TCP Recovery With Natural Refresh</div><div class="line"><a name="l00102"></a><span class="lineno"> 102</span>&#160;</div><div class="line"><a name="l00103"></a><span class="lineno"> 103</span>&#160;Previously, it was not possible to use TCP recovery service while maintaining </div><div class="line"><a name="l00104"></a><span class="lineno"> 104</span>&#160;order books in natural refresh mode. Starting with version 4 of the SDK a </div><div class="line"><a name="l00105"></a><span class="lineno"> 105</span>&#160;TCP recovery facility can be used while processing market data in any selected</div><div class="line"><a name="l00106"></a><span class="lineno"> 106</span>&#160;way. </div><div class="line"><a name="l00107"></a><span class="lineno"> 107</span>&#160;</div><div class="line"><a name="l00108"></a><span class="lineno"> 108</span>&#160;\section new-book-management Book Management Improvements</div><div class="line"><a name="l00109"></a><span class="lineno"> 109</span>&#160;</div><div class="line"><a name="l00110"></a><span class="lineno"> 110</span>&#160;The users must explicitly configure the Handler concerning which types </div><div class="line"><a name="l00111"></a><span class="lineno"> 111</span>&#160;of order books are to be maintained starting with the given major release. </div><div class="line"><a name="l00112"></a><span class="lineno"> 112</span>&#160;Previously, maintenance was defined by either the Handler&#39;s settings or </div><div class="line"><a name="l00113"></a><span class="lineno"> 113</span>&#160;by the fact of associating correspondent book listener with a Handler </div><div class="line"><a name="l00114"></a><span class="lineno"> 114</span>&#160;instance. See \ref book-handling for more information. </div><div class="line"><a name="l00115"></a><span class="lineno"> 115</span>&#160;</div><div class="line"><a name="l00116"></a><span class="lineno"> 116</span>&#160;\section miscellaneous-new-features Miscellaneous</div><div class="line"><a name="l00117"></a><span class="lineno"> 117</span>&#160;</div><div class="line"><a name="l00118"></a><span class="lineno"> 118</span>&#160;\ref what-is-new section enlists other features </div><div class="line"><a name="l00119"></a><span class="lineno"> 119</span>&#160;and improvements as individual topics. </div><div class="line"><a name="l00120"></a><span class="lineno"> 120</span>&#160;</div><div class="line"><a name="l00121"></a><span class="lineno"> 121</span>&#160;\see \ref migration-guide</div></div><!-- fragment --></div><!-- contents -->
<!-- HTML footer for doxygen 1.8.11-->
<!-- start footer part -->
<footer>
<hr class="footer"/>
<address class="footer">
<small>&copy; <a href="http://www.onixs.biz">Onix Solutions [On<span class="corporate-orange">i</span>x<span class="corporate-orange">S</span>]</a>. All rights reserved.</small>
</address>
</footer>
</div> <!-- wrapper -->
</body>
</html>