Basic support for event history

#1

Hi,

in a customer application, we now had the need for retrieving history of sensor event streams - in a simple and light-weight way.

As we had this idea floating around for some time for WAMP in general, and Crossbar.io in partricular, I took the chance to actually write some code;)

So here yoou are: trunk now has basic support for event history.

Here is a complete example and description

https://github.com/crossbario/crossbarexamples/tree/master/event-history

Please try it out and let me know what you think! Any feedback welcome.

Cheers,
/Tobias

0 Likes

#2

in a customer application, we now had the need for retrieving history of
sensor event streams - in a simple and light-weight way.

This is nice - will this allow my clients to fetch missed messages/events when it connects after being offline? Or is ‘message persistence’ something that is coming later? (If later, do you have an approx eta?)

Thanks!

0 Likes

#3

Hi Tim!

With the event history feature your clients can fetch missed events if message persistence is configured for the respective topic.

Regards,

Alex

···

Am Montag, 23. November 2015 22:51:04 UTC+1 schrieb Tim Keeler:

in a customer application, we now had the need for retrieving history of
sensor event streams - in a simple and light-weight way.

This is nice - will this allow my clients to fetch missed messages/events when it connects after being offline? Or is ‘message persistence’ something that is coming later? (If later, do you have an approx eta?)

Thanks!

0 Likes

#4

Great it’s way better then the solution I’ve been using.

···

On Tue, Nov 24, 2015 at 10:46 AM, Alexander Gödde alexande...@googlemail.com wrote:

Hi Tim!

With the event history feature your clients can fetch missed events if message persistence is configured for the respective topic.

Regards,

Alex

Am Montag, 23. November 2015 22:51:04 UTC+1 schrieb Tim Keeler:

in a customer application, we now had the need for retrieving history of
sensor event streams - in a simple and light-weight way.

This is nice - will this allow my clients to fetch missed messages/events when it connects after being offline? Or is ‘message persistence’ something that is coming later? (If later, do you have an approx eta?)

Thanks!

You received this message because you are subscribed to the Google Groups “Crossbar” group.

To unsubscribe from this group and stop receiving emails from it, send an email to crossbario+...@googlegroups.com.

To post to this group, send email to cross...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/crossbario/594e5210-7297-42b8-a320-084ba14c76f3%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Johnny W. dos Santos

0 Likes

#5

Yes, it will allow a reconnecting client to catch up on missed events.

However, if you restart Crossbar.io, the history is lost.

We’ll add persistent message history later. When that is done, the history will survive restarts of Crossbar.io itself also.

···

Am Montag, 23. November 2015 22:51:04 UTC+1 schrieb Tim Keeler:

in a customer application, we now had the need for retrieving history of
sensor event streams - in a simple and light-weight way.

This is nice - will this allow my clients to fetch missed messages/events when it connects after being offline? Or is ‘message persistence’ something that is coming later? (If later, do you have an approx eta?)

Thanks!

0 Likes