Crossbar.io event history

#1

First off, my compliments on a very promising and open project.
I just discovered it and was thinking of using it at our next Raspberry Jam where the co-working space that hosts us asked if it’s possible to make a digital self-service visitor desk in the lobby.

visitor comes in > indicates who they’re visiting > target gets alerted on his/her phone or at his/her desk

I saw that event history is foreseen in WAMPv2 and planned(?) in crossbar, so I wanted to ask:

  • what is the current state and how/when is this expected to evolve in the future?

  • what is the current recommended practice for catching up with “missed” messages and/or persisting/replaying events (e.g. in a DB?)

-feel free to keep it short and/or point me to existing resources I may have missed-

FWIW I fully support the clear separation between Autobahn and crossbar.io :slight_smile:

Thanks!

Dirk

Note: I’m also looking at using crossbar at work as a logging / communication hub for a docker-based on-demand scientific simulation cluster we are building, but that’s a story for a different time :slight_smile:

0 Likes

#2

Dirk,

First off, my compliments on a very promising and open project.

Thanks!

I just discovered it and was thinking of using it at our next Raspberry
Jam where the co-working space that hosts us asked if it's possible to
make a digital self-service visitor desk in the lobby.
visitor comes in > indicates who they're visiting > target gets alerted
on his/her phone or at his/her desk

I saw that event history is foreseen in WAMPv2 and planned(?) in
crossbar, so I wanted to ask:
- what is the current state and how/when is this expected to evolve in
the future?

Features like from "last message on subscribe" up to full message persistence / history is currently in "spec stage". But it's not yet there .. neither in spec, nor in Crossbar.io (or any other router I am aware).

- what is the current recommended practice for catching up with "missed"
messages and/or persisting/replaying events (e.g. in a DB?)

The idiom we use most often, e.g. for accessing a variable X residing in some backend component is to expose X via a "get_x" WAMP procedure, plus event "on_x" with value updates triggered from "set_x".

I do understand that this isn't quite the same as what router built-in mechanisms could provide.

-feel free to keep it short and/or point me to existing resources I may
have missed-
FWIW I fully support the clear separation between Autobahn and
crossbar.io :slight_smile:

:wink:

Cheers,
/Tobias

···

Am 25.12.2014 um 18:50 schrieb Dirk Devriendt:

Thanks!
Dirk

Note: I'm also looking at using crossbar at work as a logging /
communication hub for a docker-based on-demand scientific simulation
cluster we are building, but that's a story for a different time :slight_smile:

--
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com
<mailto:autobahnws+...@googlegroups.com>.
To post to this group, send email to autob...@googlegroups.com
<mailto:autob...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/autobahnws/cc7656c2-1e6c-46e3-a38b-b29e0f81baf6%40googlegroups.com
<https://groups.google.com/d/msgid/autobahnws/cc7656c2-1e6c-46e3-a38b-b29e0f81baf6%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

0 Likes