I know you have little time, I'm justing pushing ideas in the suggestion
box, don't mind me.
No, this is highly welcome! Thanks for the pointers/thoughts. I am definitely interested in findings like these .. my radar reach is limited;)
I can see at leat 2 libraries that would benefit from a WAMP client
Circuit : http://circuitsframework.com/
It's pure Python and works from 2.6 to 3.4. A good alternative to
trollus and doesn't require any compilation.
I've been skimming over the docs of circuits a little. Here are my thoughts:
- they talk "components" .. which is interesting. However, I think what they mean is more like a component framework for within Python-only programs, not general cross-language, networked components
- they have invented their own asynchronous networking stuff under the hood (not using any Twisted, asyncio/Trollius, etc). Huh. I think this is a bad idea. Python definitely does not lack in options here. In fact, it is my view that Python is at a distinct disadvantage compared to Node for example. In Node, there is _one_ way of doing anything async. - network, disk, whatever. That is _huge_. Python is fragmented in this respect.
This latter is a bummer for me. Why reinvent the wheel (asynch networking) .. a 5th time?
But there is a least-common denominator integration point into WAMP:
Crossbar.io supports a REST-WAMP bridge (currently only Publisher role, but the other 3 are just a matter of getting it done).
I think we talked about it last year. It's more about getting the gevent
community in the boat with us.
gevent-websocket _seems_ to be the "way to go" when doing WebSocket on gevent .. not aware of any other lib.
Regarding support for Python networking frameworks in general:
- Twisted -> AutobahnPython
- asyncio/Trollius -> AutobahnPython
- gevent -> gevent-websocket
- Tornado -> https://github.com/tavendo/AutobahnPython/issues/314
Are there any more (significant)?
Am 04.01.2015 um 07:55 schrieb Michel Desmoulin: