Fwd: Telegraphy

[Nahuel Defossé]

Forward this discussion to Telegraphy's group in order to continue discussion with broader audience.

---------- Forwarded message ----------
From: Tobias Oberstein <tobias.o...@gmail.com>
Date: 2014-07-04 9:30 GMT-03:00
Subject: Re: Telegraphy
To: Nahuel Defossé <nahuel....@gmail.com>


Hi Nahuel,

Am 04.07.2014 13:49, schrieb Nahuel Defossé:

Hi Tobias!

One of telegraphy's goals for its next iteration is to migrate to wamp2.

great!

It's quite likely we'll be starting to work on that next week, and I'm
quite sure I'll be checking out crossbar. Xmlrpc does not fit for heavy
load, and redis or amqp require too much effort at the moment.

here are a couple of +1 for crossbar (my view):

the push endpoint of crossbar uses JSON (already much more efficient than XML), and we can easily add MsgPack too (can be even more efficient than JSON).

the push endpoint supports secure and signed pushes, and also access restriction by IP.

of course it also supports HTTP 1.1 persistent connections.

all of above means: it's quite production ready.

crossbar also supports 18 WAMP2 transports in total (incl. HTTP longpoll fallback for old browsers):

https://github.com/crossbario/crossbar/wiki/Crossbar.io-Transports

then crossbar has multiple WAMP authentication mechanisms built in.

and there are plans to extend the "push service" to a full flavored, two-way WAMP bridge

I'll be on the irc channel as D3f0.

perfect. when you don't find me there, quickest way to reach me is pinging via twitter (oberstet)

Cheers
Nahuel

Ps: will be you attendig europython 2014? My fiancee gives a talk and I
came to germany with her so I'll be there too and it'll be great to mee
you IRL

unfortunately not. I am just too heavily loaded with stuff;(

Cheers,
/Tobias

El jul 4, 2014 12:58 PM, "Tobias Oberstein" <tobias.o...@gmail.com

<mailto:tobias.oberstein@gmail.com>> escribió:

    Hi Nahuel,

    my name is Tobias, I am developer with the Autobahn project.

    I just stumbled across Telegraphy (wasn't aware it exists) and
    wanted to start a little dicussion - if you are interested.

    As far as I understand, the core of what Telegraphy provides is:

    http://telegraphy.readthedocs.__org/en/latest/django-__telegraphy.html#class-based-__events-generation

    <http://telegraphy.readthedocs.org/en/latest/django-telegraphy.html#class-based-events-generation>

     From what I understand (I am not using Django), this looks really
    nice, useful and convenient. I like it.

    Now, Telegraphy

    1) comes with an XMLRPC based gateway for pushing events from within
    Django

    2) is using WAMP1 (and an old Autobahn version)

    Not sure if you are aware of

    https://github.com/crossbario/__crossbar

    <https://github.com/crossbario/crossbar>

    In short: this is a production ready, fully supported WAMP2 router
    based on Autobahn with _lots_ of features.

    One of those features is:

    https://github.com/crossbario/__crossbar/wiki/HTTP-Pusher-__Service

    <https://github.com/crossbario/crossbar/wiki/HTTP-Pusher-Service>

    This push API is properly spec'ed and supported.

    I am wondering if it would make sense for Telegraphy to build on
    that push API / service.

    That would immediately provide WAMP2 support for Telegraphy and
    remove the embedded gateway in Telegraphy among others.

    Thoughts?

    Cheers,
    /Tobias