Hi,
>> We are using the autobahn/trollius framework for inter-process
communication
of a Python-COM-component within a .NET-GUI-Application with a HTML5 based
presentation component.
Nice!
OT: Curious: so on the WAMP side, you are using AutobahnJS and
AutobahnPython, but no native .NET WAMP client library (like eg
https://github.com/Code-Sharp/WampSharp)?
That's great stuff, since even events can be sent easily.
We definitely have to stick to Python 2.7 for the next coming years.
So we really appreciate your work (and the autobahn folks as well ...) and
Thanks;)
hope that this technology can be maintained for a while.
Hum, in fact I was not really prepared to such reply :-)
To be clear: I'm *not* interested to maintain Trollius anymore. I'm
not following anymore the latest changes made in asyncio, so it became
harder for me to update Trollius.
Trollius is a fork of the asyncio git repository. To update Trollius
to retrieve latest asyncio changes, you have to fix a lot of subtle
issues for Python 2 (Python 3 language is simpler!).
I can understand Victor. As he pointed out, his original goal (moving
OpenStack to a more modern networking stack) didn't work out for
reasons. So motiviation (and I guess) time is the limit.
@Matthias: rgd AutobahnPython: if you are stuck on Python 2, and if
Trollius is should really go away, that will leave Twisted as the
underlying networking stack. You could either use Twisted fully at app
surface also (like when using @inlineCallbacks for co-routines), or you
could use txaio at the app level, write your code against these idioms,
and then the code will run anywhere: Py2 or 3, asyncio/Trollius or Twisted.
Of course there is a price: no co-routine style for example. But that's
how Autobahn itself is written under the hood (one code base). So it
works, and we'll be supporting txaio.
Probably you already knew all that - just wanted to mention in case not.
Cheers,
/Tobias
Victor
