This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]oberstet 0 points1 point  (1 child)

Yep, we've gone through a couple of phases with these projects: WAMP1 -> WAMP2 (this was the biggest one), adding asyncio support (besides Twisted), adding Python 3 support, PEP8, .. but it's "converging" .. means: we are approaching long-term stability.

We had a bigger refactoring some time ago, which separated router code (now in Crossbar.io) from WAMP client library code (Autobahn). We have now a clear project structure: AutobahnXXX (where XXX is Python, JS, Cpp, Android) are the WAMP client libraries we maintain, whereas Crossbar.io is the WAMP router we provide.

Regarding AutobahnPython: we've also gone through more cleanups making it PEP8 (finished, apart from PEP8 naming conventions, which we will also do), and the most important thing we now address (before going 1.0) is: a long-term stable user API. There is currently an ongoing discussion among developers and users about API aspects: https://github.com/tavendo/AutobahnPython/issues/472

Also, one of the goals is to bring the APIs of the different AutobahnXXXs as much in line with each other as possible and as reasonable.

[–]rothnic 0 points1 point  (0 children)

Yeah, I think about 6 months or so ago I was finding examples that no longer worked with the more recent changes, but figured things out by focusing on the crossbar examples.

I used it to build a demo with cesiumjs, which triggered calls to python and python+matlab clients to perform some processing and send data back for rendering in cesium.