Closed oberstet closed 2 years ago
depends on https://github.com/crossbario/cfxdb/pull/88
alright, finally, crossbar 22.4.1 has this fixed. a complete test of WAMP-CRA with persistent cookie database and persistent realm store, and with a proxy-router cluster setup is here
here are some screenshots of the router side.
correct (proxy frontend) transport information incl. cookies is provided in the meta API event, and is identical to what is returned via meta API procedure:
and data is persisted in DB, including proxy frontend and backend transport information
and the WAMP meta API info for the session is still accessible once the session is gone
and it will be available in all router workers, and across router restarts.
Extend the meta API to retrieve session (and transport) details
https://github.com/crossbario/crossbar/blob/33f48c81595427942935f66e352025674962a51a/crossbar/router/service.py#L230
to allow to retrieve closed session data.
To avoid complex state handling, and to support multi-node configurations, the session data should be persisted in a database table backed session store in case historic session data API is used.
This will also solve the following common problem: once the meta API has notified observers that a session has left, the session/transport details for that session can no longer be retrieved:
example from https://github.com/crossbario/crossbar-examples/pull/151