Databases
StackOverflow2013
Postsdbo
POUsing reactive extensions to hold onto the most recent event in a series of events until x seconds after most recent event has been received
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing reactive extensions to hold onto the most recent event in a series of events until x seconds after most recent event has been received
    primarykey
    data
    text
    <p>I am trying to understand how the following scenario could be implemented using reactive extensions. Other solutions that I have been looking at involve managing a series of timers... something that I am looking to avoid if possible.</p> <p><strong>Scenario</strong><br> A stream of "ActionRequests" occurring. The ActionRequest's streaming in are from different object sources. I am only interested in picking off the most recent ActionRequest once requests have stopped coming in from a specific source for a period of x seconds</p> <p>So breaking that down. <Li>Events are being continuously received from different object sources. <Li>The different object sources are denoted by a guid - see the ActionRequests class <Li>After x number of seconds of silence from the object source the latest event is pushed out. <Li>The older messages can be discarded once a more recent ActionRequest of interest has been received</p> <pre><code>public class ActionRequest { public ActionRequest(Guid quoteId, DateTime now) { QuoteId = quoteId; RequestTimestamp = now; } public Guid QuoteId { get; set; } public DateTime RequestTimestamp { get; set; } } </code></pre> <p>Any thoughts on this would be appreciated.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAdrian Russell
    1. USAdrian Russell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing reactive extensions to hold onto the most recent event in a series of events until x seconds after most recent event has been received
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUsing reactive extensions to hold onto the most recent event in a series of events until x seconds after most recent event has been received
      1. USLee Grissom
      1. VTFavorite
    1. CODo you actually have to buffer the events for some reason, or do you just want to respond to the latest event after x seconds of "silence", thus skipping the earlier events?
      singulars
      1. POUsing reactive extensions to hold onto the most recent event in a series of events until x seconds after most recent event has been received
      1. USRichard Hein
    2. COThat is a good question. It would not really be necessary to buffer all of the events, just as long as the most recent event for each QuoteId was pushed out after a period of silence. I will update
      singulars
      1. POUsing reactive extensions to hold onto the most recent event in a series of events until x seconds after most recent event has been received
      1. USAdrian Russell
    3. COThen Observable.Throttle should do it, like Dave said in the Rx Forums. No?
      singulars
      1. POUsing reactive extensions to hold onto the most recent event in a series of events until x seconds after most recent event has been received
      1. USRichard Hein
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload