I guess exactly the last point. Using a header is not the difficulty, more using the API in a client application.
I understand due to C++ and futures the WAMP initialization (connect, session, joined) needs to be nested. I thought someone have come up with a easier to use (API wise) wrapper around this.
For example if the user wants to dynamically subscribe to topics, he can only register them after a joined. Ideally the user can register at any time, e.g. using an internal message queue, where requests are stored. Whent the client then goes online the queue is processed automatically.
Or a C++ client where I can register callbacks when session is joined, with the session as parameter. But maybe it’s just the way C++ works.
Just to be clear, I don’t expect wamp/c++ will offers this, I am looking more if there are larger examples/demos out there where they solved these problems already.