SL4B Examples: Filtering

This page demonstrates the use of filters to show only records that match certain conditions. Please click here for more information on how this page has been configured.

This display is split up into three sections. The top section shows the unfiltered record updates, whilst the central section shows record updates received for various image filters and the the bottom section updates for update filters. Please see the SL4B_AbstractRttpProvider.getFilteredObject() method for more infomation on filtering.

An image filter means a new update will be received if the filter is true for the new image of the object, that means the current value of all fields after this update is applied. If a user is subscribed to an object with an image filter of Ask>10 and the object contains Bid=9.9 and Ask=10.1, if an update with Bid=9.8 is received the user will receive that update since Ask>10 is still true.

With an update filter the update will only be received if that update alone matches the subscribed filter. If a user is subscribed to an object with an update filter of Ask>10 and the object contains Bid=9.9 and Ask=10.1Bid=9.8 is received the user will not receive that update since it does not even contain an Ask value, therefore Ask>10 is not true.


MSFT

Filter Bid Ask Last Time VolumeAcc
No Filter - - - - -
Image Filters
Bid<33 - - - - -
Bid>33 & Bid<35 - - - - -
Bid>35 & Bid<36 - - - - -
Bid>33 - - - - -
Update Filters
Ask<33 - - - - -
Ask>33 & Ask<35 - - - - -
Ask>35 & Ask<36 - - - - -
Ask>33 - - - - -