Thanks Meejah. Appreciate your clearing up that Flask is not based on
twisted, not sure I got that impression earlier.
Checked Klein, and it seems quite promising (and seem quite similar to
Flask, from developer standpoint). From the documentation it was not quite
evident to me, as to how to use HTTP2 under Klein.
I did find a reference to HTTP2 in this pull-request, but again not clear
to me: https://github.com/twisted/klein/pull/113

Checked treq, but is it really advantageous over request ? Also found no
reference to HTTP2 in treq documents.

Alao thanks for the references to Crossbar.io and Autobahn. Will check them
out shortly.

cheers,
Jay


On Fri, May 24, 2019 at 7:52 PM meejah <mee...@meejah.ca> wrote:

> Jayanth Acharya <jayacha...@gmail.com> writes:
>
> > From a very quick read of the Twisted docs (and some stackoverflow
> > Q&A) I get the impression that it is possible to use Flask as the
> > RESTful web-service framework using HTTP/2.0 for the server-end, but
> > perhaps there is no Twisted framework provided HTTP/2.0 client at
> > similar level of abstraction, and one perhaps needs to use hyper-h2 at
> > more nuts-n-bolts level. I hope I am completely wrong on the latter
> > part.
>
> Flask is a threaded/synchronous framework. Klein provides something
> similar based on Twisted on the server-side, and treq provides something
> like requests at the client side.
>
> Depending on what you're doing, you might also be interested in
> Crossbar.io and Autobahn which provide RPC and PubSub services. There is
> a "REST Bridge" here to bridge from plain HTTP (including HTTP/2)
> services to the WAMP protocol (which does RPC and PubSub).
>
> --
> meejah
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Reply via email to