AutobahnCpp has a number of issues that I think are quite severe:
In addition, it depends on experimental boost_thread features for its core operation, and has very minimal test coverage. Also, the use of boost::any rather than a proper variant type also makes for a fairly painful user experience.
It’s not too much work to cut over from AutobahnCpp to CppWAMP, and the latter library is significantly more mature and feature complete. I strongly recommend doing so if it’s an option for you.
In the end it’s of course up to you, but with the current implementation, I think it’s unlikely for AutobahnCpp to become suitable for production code without what would substantially be a rewrite with major breaking API changes. I don’t doubt that it will eventually be fixed, but I am much happier to not be using AutobahnCpp for the time being.
On Thursday, May 14, 2015 at 5:12:51 PM UTC-4, Rosa Lisin wrote:
Thanks, I’ll check it out. However, given that fact that I’ve invested quite some time already into autobahnCpp and part of the system uses autobahnPython, I’d prefer to stick with autobahnCpp, if the said features are going to be implemented in the neasr future.
On Thursday, May 14, 2015 at 1:12:53 PM UTC-4, Jimmy Jia wrote:
Oops, I am not sure how I messed up the link that badly. Of course it’s: https://github.com/ecorm/cppwamp
On Thursday, May 14, 2015 at 1:12:24 PM UTC-4, Jimmy Jia wrote:
I would take a look at CppWAMP: https://github.com/react-bootstrap/react-bootstrap/issues/641
It’s a lot more complete and mature than AutobahnCpp, and I believe has support for the things you were mentioning (predefined WAMP errors are mapped to error codes, other error URIs show up in error description), plus much much less brokenness than AutobahnCpp with its async handling.
I recently cut over my code from AutobahnCpp to CppWAMP, and have been quite happy so far.
On Wednesday, May 13, 2015 at 12:59:26 PM UTC-4, Rosa Lisin wrote:
- Pattern based topic subscription support (subscription options are not implemented)
- Topic unsubscription support (unsubscribe method is not implemented)
- Custom exception propagation (if remote procedure throws custom exception, the caller receives a generic wamp.error).
Are there any plans to implemet these features? If yes, then when do you expect them to be available?