On 2014-02-18 13:31, chrysn wrote:
hello pocoo people,
On Sun, Feb 16, 2014 at 02:45:46PM +0100, chrysn wrote:
i've assembled a minimal working example on [1] (see there for source,
links, and further comments); it demos a server that serves flask
applications and also routes an eventsource resource, which sends an
update to the browser every two seconds.
this has sparked some discussion on the python-tulip mailing list[1];
especially, don brown and aymeric augustin told about their own
attempts
with flask[2] and django[3], respectively.
an issue that came up and is more-or-less solved (works, but by
monkey-patching python core libraries, so it would need adaptions to
every single asyncio main loop) is the concept of having thread-local
variables that indicate the current meaning of 'flask.request'.
am i right assuming that it's a design decision of flask/werkzeug not
to
pass those references around explicitly?
Yes.
do you think the approach of [2] is feasible for future asyncio backend
support in werkzeug?
Which exact changes do you mean? I looked a bit in that repository and
at least the code in werkzeug.local doesn't seem to have changed. The
recent commits by mrdon are also unrelated.
best regards
chrysn
[1] https://groups.google.com/forum/#!topic/python-tulip/lW_I_13LDyg
[2] https://github.com/mrdon/flask
[3] https://github.com/aaugustin/django-c10k-demo
--
You received this message because you are subscribed to the Google Groups
"pocoo-libs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pocoo-libs.
For more options, visit https://groups.google.com/groups/opt_out.
