Files
externals/linux/doc/Onixs.CME.4.8.0/html/group__migration-guide.html

220 lines
26 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: Migration Guide</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 class="current"><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><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
</div><!-- top -->
<div class="header">
<div class="headertitle">
<div class="title">Migration Guide</div> </div>
</div><!--header-->
<div class="contents">
<p>Although given release is based on the same processing core as a previous major version release, a lot of aspects have been principally redesigned and improved. Given section covers major differences for painless migration from previous releases.</p>
<h1><a class="anchor" id="migrate-listener-consolidation"></a>
Consolidated Listeners</h1>
<p>In previous generations of SDK, listeners were designed to cover smallest aspects of market data processingand thus API contained bunch of listeners to be used to get market-related events handled in a regular application. For example, there was a <code>OnixS::CME::MDP3::SecurityDefinitionListener</code> whose members were involved once instrument definition was received and updated. For each type of book there was corresponding listener exposing books after updates. Atomic book changes could be accessed through another set of listeners.</p>
<p>To reduce overhead caused by necessity of using wide range of listeners and to bring more clarity, most of listeners have been consolidated.</p>
<p>Primary principle was to consolidated Handler, Market Data (message) and Security related events. Table below depicts basic correspondence between old and new listeners.</p>
<table class="doxtable">
<tr>
<th>Old Listeners </th><th>New Listener </th><th>Notes </th></tr>
<tr>
<td><code>OnixS::CME::MDP3::HandlerStateChangeListener</code> <code>OnixS::CME::MDP3::WarningListener</code> <code>OnixS::CME::MDP3::ErrorListener</code> </td><td><code><a class="el" href="structOnixS_1_1CME_1_1MDH_1_1HandlerListener.html" title="Events raised by Handler while processing market data. ">OnixS::CME::MDH::HandlerListener</a></code> </td><td>State change and issue (warning, error) events were merged into the new listener containing callbacks which are invoked to notify users on various aspects of market data processing by Handler. </td></tr>
<tr>
<td><code>OnixS::CME::MDP3::MessageProcessingListener</code> <code>OnixS::CME::MDP3::EventMessageListener</code> <code>OnixS::CME::MDP3::EventListener</code> </td><td><code><a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html">OnixS::CME::MDH::MarketDataListener</a></code> </td><td><p class="starttd"><a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html">OnixS::CME::MDH::MarketDataListener</a> represents adoptation of <code>OnixS::CME::MDP3::MessageProcessingListener</code> to the new messaging subsystem. Since unified FIX message container was substituted with typified SBE messages as they are defined in CME specification, listener was enhanced with overloads for each type of new message.</p>
<p class="endtd">Also, new members defining bounds of packet processing have been added. For this reason old <code>EventMessageListener</code> and <code>EventListener</code> listeners were removed from API as the improved market data listener allows to implement given event in easy way. </p>
</td></tr>
<tr>
<td><p class="starttd"><code>OnixS::CME::MDP3::SecurityDefinitionListener</code></p>
<p><code>OnixS::CME::MDP3::MboBookUpdateListener</code> <code>OnixS::CME::MDP3::DirectBookUpdateListener</code> <code>OnixS::CME::MDP3::ImpliedBookUpdateListener</code> <code>OnixS::CME::MDP3::ConsolidatedBookUpdateListener</code></p>
<p><code>OnixS::CME::MDP3::MboBookChangeListener</code> <code>OnixS::CME::MDP3::DirectBookChangeListener</code> <code>OnixS::CME::MDP3::ImpliedBookChangeListener</code></p>
<p><code>OnixS::CME::MDP3::TradeListener</code> <code>OnixS::CME::MDP3::OrderIdListener</code> <code>OnixS::CME::MDP3::ElectronicVolumeListener</code></p>
<p><code>OnixS::CME::MDP3::StatisticsListener</code></p>
<p><code>OnixS::CME::MDP3::SecurityStatusListener</code></p>
<p class="endtd"><code>OnixS::CME::MDP3::RequestForQuoteListener</code> </p>
</td><td><code><a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html" title="Callbacks invoked by Handler to expose market data entities. ">OnixS::CME::MDH::SecurityListener</a></code> </td><td><p class="starttd">Security-related events are now consolidated into single listener.</p>
<p>Following important changes were done in the how particular cases are handled:</p>
<ul>
<li>Unknown security definitions are now exposed through the <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#acb157c7684b2328fa1890c8a9ef08ce3">OnixS::CME::MDH::SecurityListener::onUndefined</a> member which also allows to update security attributes like security group, asset, etc. Previously, unknown securities were not exposed through security definition listeners. Instead, Handler raised a warning on absence of definition.</li>
<li>Trade summary processing has been reworked. Previously, SDK exposed separate listeners for trades and order identifiers providing special indexing for linking order ids with the trades. Now, trades are always reported through the same <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#af48a587cbb86ca8833d24d0d779d399b">OnixS::CME::MDH::SecurityListener::onTrade</a> callback. Order ids refering to a particular trade summary can be gathered by the Handler and delivered together with a trade summary instance depending on a trade summary handling strategy controlled by <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1HandlerSettings.html#a0978253f4b010d6957aba107fd51c2ff" title="Indicates how trades are processed. ">OnixS::CME::MDH::HandlerSettings::tradeProcessing</a> parameter value. See <a class="el" href="group__trade-order-details.html">Trade Order Details</a> for more information.</li>
<li>Previously, maintenance of books of a particular type was enabled by Handler basing on registering instance of listener for that kind of books. Now, as Book update callbacks consolidated into single listener together with the other events maintenance is explicitly defined by corresponding parameters which define whether particular overload of <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#a9a81ad09e17caf95e9d24941dbe7c98b">OnixS::CME::MDH::SecurityListener::onBookUpdate</a> will be invoked by the Handler or not. </li>
</ul>
</td></tr>
</table>
<h1><a class="anchor" id="migrate-book-management"></a>
Book Management</h1>
<p>Previously, maitenance of books of particular type (MBO, direct, implied, consolidated) was automatically enabled by Handler if either corresponding listener was associated with an instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html">OnixS::CME::MDH::Handler</a> or book maintenance was forcibly enabled through Handler's settings.</p>
<p>Also, depending on which listeners are registered (for example, listener for atomic changes in direct order book), Handler selected appropriate source of recovery data to catch-up up-to-date market state during late join or after detecting gap in incremental data. For example, if user was interested in receiving MBO book updates without subscribing to MBP book updates, Handler listened to recovery data on MBO snapshot feed only without joining snapshot feed for MBP books.</p>
<p>In given release, Handler's behavior has been improved to be more clear for the users.</p>
<p>Book updates are now exposed through <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#a9a81ad09e17caf95e9d24941dbe7c98b">OnixS::CME::MDH::SecurityListener::onBookUpdate</a> members of consolidated listener for security-related data. However, overriding noted virtual member doesn't mean subscribing to a book updates. Book maintenance is explicitly defined by corresponding parameter from <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1HandlerSettings.html#a5ca02fce213b94af7f14667340188a0a" title="Reference to parameters affecting book management. ">OnixS::CME::MDH::HandlerSettings::bookManagement()</a> section:</p>
<table class="doxtable">
<tr>
<th>Parameter Path </th><th>Description </th></tr>
<tr>
<td><code>handlerSettings.bookManagement().mboBooks().maintain(bool status)</code> </td><td>Enables or disables MBO books maintenance </td></tr>
<tr>
<td><code>handlerSettings.bookManagement().directBooks().maintain(bool status)</code> </td><td>Enables or disables direct books maintenance </td></tr>
<tr>
<td><code>handlerSettings.bookManagement().impliedBooks().maintain(bool status)</code> </td><td>Enables or disables implied books maintenance </td></tr>
<tr>
<td><code>handlerSettings.bookManagement().consolidatedBooks().maintain(bool status)</code> </td><td>Enables or disables consolidated books maintenance </td></tr>
</table>
<p>Once parameter is turned on, Handler invokes <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#a9a81ad09e17caf95e9d24941dbe7c98b">OnixS::CME::MDH::SecurityListener::onBookUpdate</a> overload corresponding to the type of book.</p>
<p>Also, behavior of the Handler in case of market recovery is now controlled by <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1SessionSettings.html#a6626a6db6b58d510918eb2ac164e14d6">OnixS::CME::MDH::SessionSettings::marketRecovery</a> parameter. It allows to define explicitly whether Handler must listen and process data from either MBO snapshot feed or MBP snapshot feed or both feeds.</p>
<p>Given improvement in behavior of the Handler allows users to obtain desired processing behavior without involving book maintenance.</p>
<h1><a class="anchor" id="migrate-books"></a>
Book Classes</h1>
<p>Book classes have been cleaned up. OnixS::CME::MDP3::BookBase::securityId and OnixS::CME::MDP3::BookBase::lastAppliedSecurityLevelSeqNumber members have been removed.</p>
<p>Data exposed by eliminated members is now consolidated into a new <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Security.html" title="Attributes associated with security. ">OnixS::CME::MDH::Security</a> class, containing all security-related attributes. Instances of given class are exposed in all callbacks of <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html" title="Callbacks invoked by Handler to expose market data entities. ">OnixS::CME::MDH::SecurityListener</a> listener. Therefore, security identifier and instrument-level sequence number are now available for trade and statistics events.</p>
<table class="doxtable">
<tr>
<th>Old Member </th><th>New Member </th><th>Description </th></tr>
<tr>
<td><code>OnixS::CME::MDP3::BookBase::securityId</code> </td><td><code><a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Security.html#a901e3a47c0d6256a7b4c32ca9fb0e362">OnixS::CME::MDH::Security::id</a></code> </td><td>Security id relocated from book to security instance </td></tr>
<tr>
<td><code>OnixS::CME::MDP3::BookBase::lastAppliedSecurityLevelSeqNumber</code> </td><td><code><a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Security.html#aff22655466b3cb2ecf1bc84c92f1a00f" title="Security-level sequence number. ">OnixS::CME::MDH::Security::seqNumber</a></code> </td><td>Now available in other security-related callbacks </td></tr>
</table>
<h1><a class="anchor" id="migrate-feed-engine"></a>
Feed Engine</h1>
<p>Concept of <a class="el" href="group__feed-engine.html">Setting Up Feed Engine</a> was introduced in previous major release of the SDK and given release inherits given concept. However, a few important changes have been made.</p>
<p>Previosly, to provide backward compatibility with older minor releases, feed engine could be constructed explicitly and bound with <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html">OnixS::CME::MDH::Handler</a> instances. If no instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1FeedEngine.html" title="Manages processing machinery for market data received from feeds. ">OnixS::CME::MDH::FeedEngine</a> was associated with an instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html">OnixS::CME::MDH::Handler</a>, then Handler constructed private instance of the feed engine.</p>
<p>In given release, implicit construction has been eliminated to provide better clarity on Handler behavior and use of system resources. Therefore, to make live market data processing happen, instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1FeedEngine.html" title="Manages processing machinery for market data received from feeds. ">OnixS::CME::MDH::FeedEngine</a> must be constructed and bound to the instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html">OnixS::CME::MDH::Handler</a>.</p>
<dl class="section note"><dt>Note</dt><dd>There's no limitation on number of feed engine instances constructed. Therefore, having single instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1FeedEngine.html" title="Manages processing machinery for market data received from feeds. ">OnixS::CME::MDH::FeedEngine</a> for each instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html">OnixS::CME::MDH::Handler</a> can be easy be achieved by constructing and binding pair of instances.</dd></dl>
<h1><a class="anchor" id="migrate-feed-events"></a>
Feed Events</h1>
<p>Feed-related events have been redesigned. First of all, direct access to sockets used to listen to multicast data has been eliminated. OnixS::CME::MDP3::FeedSocket class is not available any more. Feed identification in events have been improved and now feed is identified by <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1NetFeed.html" title="Base attributes of market data feed. ">OnixS::CME::MDH::NetFeed</a> class containing primary attributes of the feed which caused an event.</p>
<p>Event listener was enhanced with a new member <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1FeedListener.html#a3649aa8cca75d74dc8d0e28e53b37dd8">OnixS::CME::MDH::FeedListener::onFeedPacket</a> allowing to trace market data received by the Handler on a particular feed. An important difference between this callback and the one in <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html">OnixS::CME::MDH::MarketDataListener</a> is that given callback is invoked by Handler every time data is received no matter whether this is duplicated or out-of-order data. Given enhancement allows to implement various tracing facilities to determine issues in data reception or its sequencing.</p>
<p>OnixS::CME::MDP3::FeedListener::onFeedSequenceIssues event and related with it functionality was removed from the Handler. Instead, <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1FeedListener.html#a3649aa8cca75d74dc8d0e28e53b37dd8">OnixS::CME::MDH::FeedListener::onFeedPacket</a> can be used to trace feeds for the issues.</p>
<h1><a class="anchor" id="migrate-instrument-cache"></a>
Instrument Definition Cache</h1>
<p>Handler exposes ability to cache instrument definitions received on live instrument feed for further reuse at late join. Previously, Handler used predefined filename and stored cache in a certain location. Therefore, settings exposed boolean parameter OnixS::CME::MDP3::HandlerSettings::cacheSecurityDefinitions which allowed to either enable or disable instrument definition caching.</p>
<p>In given release, behavior was been improved and now Handler allows to specify arbitrary filename and location. Instrument definition caching is enabled while non-empty path to the cache is specified through <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1HandlerSettings.html#a1515d673d03c09c8fb24b287e35cc513">OnixS::CME::MDH::HandlerSettings::instrumentCache</a> parameter.</p>
<h1><a class="anchor" id="migrate-message-processing"></a>
Message Processing</h1>
<p>One of major improvements done in given release is redesigned message subsystem. In previous releases, market data was exposed through the OnixS::CME::MDP3::Message class representing an unified container of FIX fields. In given release message subsystem has been redesigned. Now market data messages are exposed to the users as they are defined in XML-based specification published by CME. Given approach gives more clarity on data structure and use and increases robustness.</p>
<table class="doxtable">
<tr>
<th>3.X Release </th><th>4.X Release </th></tr>
<tr>
<td><code>OnixS::CME::MDP3::Message</code> </td><td><code>OnixS::CME::MDH::ChannelReset</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::AdminLogin</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::AdminLogout</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::InstrumentDefinitionFuture</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::InstrumentDefinitionSpread</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::InstrumentDefinitionOption</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::SecurityStatus</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshBook</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshOrderBook</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshTrade</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshTradeSummary</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshVolume</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshSessionStatistics</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshDailyStatistics</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::IncrementalRefreshLimitsBanding</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::SnapshotFullRefresh</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::SnapshotFullRefreshOrderBook</code> </td></tr>
<tr>
<td></td><td><code>OnixS::CME::MDH::QuoteRequest</code> </td></tr>
</table>
<p><a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html">OnixS::CME::MDH::MarketDataListener</a> as the listener for the received market data was enhanced with overloads for each type of SBE message.</p>
<p>Additionaly, since given release original network packets received on live feeds are exposed to the users through <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html">OnixS::CME::MDH::MarketDataListener</a> interface as instances of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Packet.html" title="Represents CME binary packet containing SBE messages. ">OnixS::CME::MDH::Packet</a> class. Correspondently, listener was enhanced with <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html#a10da35efefb7385a404335c9ba189a36" title="Invoked when processing of packet has begun. ">OnixS::CME::MDH::MarketDataListener::onPacket</a> and <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html#ae1c9e58d477cd54b46226336a3205395" title="Invoked when processing of packet has ended. ">OnixS::CME::MDH::MarketDataListener::onEndOfPacket</a> allowing to determine bounds of packet processing.</p>
<h1><a class="anchor" id="migrate-logger"></a>
Event And Data Logging</h1>
<p>Logging layer was significantly reworked and abstraction of logging service was introduced. Now users can implement their logging service including memory-based ones. SDK offers ready-to-use implementation for logging events into a file.</p>
<p>Following examples depict how to enable file-based logging for the Handler in previous and current releases:</p>
<h2><a class="anchor" id="migrate-logger-v3-sample"></a>
Enabling logging in previous generations of SDK</h2>
<div class="fragment"><div class="line">HandlerSettings handlerSettings;</div><div class="line"></div><div class="line">handlerSettings.logDirectory(<span class="stringliteral">&quot;logs&quot;</span>);</div><div class="line">handlerSettings.logMode(LogModes::Debug);</div><div class="line">handlerSettings.advancedLogOptions(AdvancedLogOptions::LogEverything);</div><div class="line"></div><div class="line">Handler handler(handlerSettings);</div></div><!-- fragment --><h2><a class="anchor" id="migrate-logger-v4-sample"></a>
Enabling logging in latest generation of SDK</h2>
<div class="fragment"><div class="line">HandlerSettings handlerSettings;</div><div class="line">..</div><div class="line">Handler handler(handlerSettings);</div><div class="line"></div><div class="line"><span class="comment">//</span></div><div class="line"></div><div class="line">FileLoggerSettings loggerSettings;</div><div class="line"></div><div class="line">loggerSettings.filename(<span class="stringliteral">&quot;LogFile.txt&quot;</span>);</div><div class="line">loggerSettings.severityLevel(LogSeverity::Debug);</div><div class="line"></div><div class="line">FileLogger logger(loggerSettings);</div><div class="line"></div><div class="line">handler.bindLogger(logger);</div></div><!-- fragment --><p>For more information see <a class="el" href="group__logging-options.html">Logging Services</a>.</p>
<h1><a class="anchor" id="migrate-replay"></a>
Log File Replay</h1>
<p>The behavior of the Handler in case of replaying a log file has been changed. In previous releases, the replay was performed asynchronously. When a user invoked the <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html#a706bb1347bedfcfd0cba2ed8d30ae5b1" title="Starts market data processing according to given parameters. ">OnixS::CME::MDH::Handler::start</a> overload, the Handler spawned a new thread. The actual log replay was done in the body of that thread. Therefore, the <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html#a706bb1347bedfcfd0cba2ed8d30ae5b1" title="Starts market data processing according to given parameters. ">OnixS::CME::MDH::Handler::start</a> overload returned control to its caller as soon as a new thread was launched. Also, the end of replay could be detected only by using a special listener designed for that purpose.</p>
<p>In the given major release, log file replay is a synchronous operation. Therefore, <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html#abe91a56751a72157fc72ac1004bf35ab">OnixS::CME::MDH::Handler::replay</a> member does not return unless a log file is replayed. The new behavior simplifies user�s interaction with the replay and reduces the use of the system resources.</p>
<p>However, the previous behavior of the replay functionality can be achieved. Users may launch additional threads and invoke the <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html#abe91a56751a72157fc72ac1004bf35ab">OnixS::CME::MDH::Handler::replay</a> in the bodies of those threads. The previous behavior is achieved in such way.</p>
<h1><a class="anchor" id="migrate-filtering"></a>
Filtering</h1>
<p>Starting from given release, SDK exposes improved filtering to the users. Previously, market data filtering was managed by set of routines exposed by the <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html">OnixS::CME::MDH::Handler</a> class like <code>OnixS::CME::MDP3::Handler::addSecurityIdFilter</code>. Also, there were inconsistency related with filtering security definitions which consisted in the fact security definitions were not filtered no matter users were interested in them or not.</p>
<p>In given release filtering was been redesigned and eliminates existent albiguities and inconsistencies available in previous releases. According to new concept, filtering is applied to security-related events consolidated into <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html" title="Callbacks invoked by Handler to expose market data entities. ">OnixS::CME::MDH::SecurityListener</a> listener. Filtering is not used by the Handler on a market data level, therefore members of <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html">OnixS::CME::MDH::MarketDataListener</a> are always invoked under same conditions and filtering has no influence on their invocation.</p>
<p>For more information on how security-related events can be filtered, see <a class="el" href="group__security-selection.html">Selecting Securities of Interest</a>. </p>
</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>