Am 26.11.2014 19:34, schrieb Dave Barndt:
Sorry, another quick question - it looks like for a Python application
session component to be run “side-by-side” with the router, it has to be
implemented with Twisted. I had started implementation using
asyncio/trollius since it seemed to be “the future” encouraged by the
asyncio is “special” in that it is part of the standard library in
Python 3.4+. asyncio also profits from the years of experience gained in
Twisted and awesome abstractions there (protocols/factories). asyncio
also profits from new language elements (“yield from”)
However, Twisted isn’t deprecated or going away. In fact, Twisted has a
lot more batteries included and broader scope than asyncio.
Python community. If I want to use asyncio, then do I have to run the
component as a guest / additional worker process?
Yes, this is correct.
Crossbar.io is written against Twisted, and Python components that run
side-by-side (in a router process) or in a container worker must be
written against Twisted also.
With guest workers, you can use anything supported by AutobahnPython:
On Wednesday, November 26, 2014 12:54:23 PM UTC-5, Dave Barndt wrote:
OK, I'll give the full Crossbar.io a go (I started with it very
early on, until I found the basic router). I hadn't downloaded it
in a while, and noticed a bunch of new examples when I updated it
yesterday. For example, I see the wss/TLS example now, which is
One quick question if I may ask (I'm sure there will be more). Is it
possible to do Linux PAM-style authentication for users connecting
to Crossbar.io/WAMP/WS? I see from the new WAMP-CRA Crossbar.io
example that a custom authentication procedure can be used, but I
assume that's only specific to WAMP-CRA.
Thanks again for all the help/guidance,
On Tuesday, November 25, 2014 3:53:08 PM UTC-5, Tobias Oberstein wrote:
Am 24.11.2014 17:03, schrieb Dave Barndt:
> Hi Tobias,
> The device has a BeagleBone Black as the CPU board - 1 GHz ARM
> Cortex-A8, 512 MB RAM, and we're expanding the flash/storage
from 4 GB
> to to 8 GB.
This is a quite beefy little machine. FWIW, it won't have any
running a full Crossbar.io.
> The reasons I was considering the basic WAMP built-in router
> essentially simplicity and ease of configuration:
> 1) I am implementing the device's WAMP endpoint in Python,
and saw that
> Autobahn Python already included the basic router.
> 2) It seemed as though I could just include the basic router
> with the application session code; seemed simple with minimal
> Based on our discussion about realms, the device could
> part of several realms (one for just itself, one for all
> one for each geographical device grouping it could belong to
> never more than a half dozen or so).
> I have nothing against using Crossbar.io in the device,
> is straightforward enough. And since this is a new,
We have a setup recipe for the Pi, which most likely will work
Beagle without modification:
I have a Beagle Black in the office (didn't have time to touch
but I might find 1-2 hours the coming weekend.
> it sounds like you are "guiding" me toward using Crossbar.io.
> think Crossbar.io will work well given the
Yes, I think so. If you only needed a WAMP component running on
device, AutobahnPython would be sufficient. In that case,
still would add value by being able to host your component in a
container which is monitored by Crossbar.io, and in the near future
would be able to remotely manage that component. If you need a
then I'd definitely recommend checking out Crossbar.io. The
above the basic router included with AutobahnPython is already
and in the coming future, you will be able to federate / hook up
locally running Crossbar.io router to a Crossbar.io instance
e.g. in a data-center. You won't be able to do that with the
You received this message because you are subscribed to the Google
Groups “Autobahn” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com
To post to this group, send email to auto...@googlegroups.com
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.