does wheezy.web support server pushing?

Create issue
Issue #23 new
Former user created an issue

i am trying to convince my boss deploy this package. however, he asked me to make http connections persistent and have server push the latest message to clients.

i am not quite familiar with web service framework. is this framework capable of doing what i was asked to do?

Comments (6)

  1. Andriy Kornatskyy repo owner

    HTTPS offload. A typical deployment is usually an application server behind a web server (e.g. nginx). This way nginx offloads https traffic so you do not have to care about it at all except some configuration changes in nginx. A communication between web server (nginx) and application server (where you have your application hosted, e.g. uwsgi) goes in plain http and as result is transparent to your application.

    Server Push. This may have deal with at least two possible scenarios: (a) data streaming (see answer here), (b) html5 sockets (full-duplex TCP connections, see discussion here and example here).

  2. Unknown Name

    hi, i tried that streaming method. i found it will block the socket for a long time. is there a way to make it concurrent?

    if a generator would block the whole application, does that mean actual the request handling is executing sequentially (without considering GIL)? can i make it concurrent in interpreter?

    since basically i need 3 parallel connections between server and each client. i don't want them to interfere each other. is that feasible?

  3. Andriy Kornatskyy repo owner

    The python standard web server is very basic and does not provide feature you are looking for. I would suggest take a look at more advanced implementation for application server which support HTML5 web sockets. Please consider take a look here:

    Both gevent/uwsgi are application servers that work nice with python… in reality they are not more that just another python package which provide WSGI application server.

    This assumes you actually need full-duplex TCP connections.

  4. Log in to comment