We develop desktop application, containing some separate services. Since we code primarily in Python, we are considering using Crossbar as a router for inter process communication messaging and also as a process manager. Base on the documentation and examples it matches our requirements quite well, but there are some issues I cannot find solution for, so I would like to ask the community for advice.
Since we develop desktop application, we cannot be sure that some specific ports are available on the client’s PC, so we cannot hardcode port numbers to the Crossbar configuration file. Typically, the solution is to make the service to bind to any available port (usually coded as port 0) and to report it to the process manager the port number it is bound to. We usually implement such reporting through named pipe which id is given to the service as a command line parameter or as value of environment variable. So I am looking for the ideas how to implement such behavior with Crossbar.
Another concern I have, is that WAMP protocol itself and all accompanying Autobahn projects are not very popular these days by some reason. For example, in spite of there are many libraries implementing WAMP, according to GitHub statistics only few of them are really actively maintained. The company Tavendo behind Autobahn and Crossbar seems to be dead, at least the copyright on tavendo.com is “Copyright © 2011-2014”. I do not see any significant activity on StackOverflow by relevant tags, strictly speaking there are some flow of questions, but most of them have no any responses. There are some dead links in the Crossbar documentation, for instance the link “Manhole” on this page. Please understand me correctly it is not critique, I am just afraid of picking dying technology for the new product. Dear colleagues, please correct me if I am wrong, I would be happy to see the elephant in the room I am missing,