I understand it's still beta but anyways, here's my little wish list for Tulip. * provide a 'demo' / 'example' directory containing very simple scripts showing the most basic usages such as: - echo_tcp_client.py - echo_tcp_server.py - echo_tcp_server_w_timeout.py (same as echo_server.py but also disconnects the client after a certain time of inactivity) - echo_tcp_ssl_client.py - echo_tcp_ssl_server.py - echo_udp_client.py - echo_udp_server.py * move all *test*.py scripts in a separate 'test' directory * if it's not part of the API intended to be public move tulip/http_client.py elsewhere ('examples'/'demo' or a brand new 'scripts'/'tools' directory) * (minor) same for check.py, crawl.py, curl.py, sslsrv.py which looks like they belong elsewhere * write a simple benchmark framework testing (at least) sending, receiving and the internal scheduler (I'd like to help with this one) --- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ http://code.google.com/p/pysendfile/
Also, I had some troubles figuring out how to run tests because setup.py doesn't actually install Tulip and "import tulip" can be used only from within the root directory.
I'm planing to work on udp support sometime next week. i'll implement echo examples except udp, later today.
Thanks. --- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ http://code.google.com/p/pysendfile/
Personally I think you'd be crazy to install this version of tulip (it's not beta, it's way before alpha!). The setup.py file only exists to build the C extension for Windows. (How to run tests is explained in README BTW. There is no boilerplate there. :-)
Sorry for the top post, but I'm on a phone. I'd love to see a trivial chat server in the demos. There are many designs for async servers that work great with echo and even http but fall down with chat (because of interactions between clients), and it would be very useful to see how tulip makes it easy to do it right. Sent from a random iPhone. On Feb 22, 2013, at 13:17, Guido van Rossum <guido@python.org> wrote:
You can check my experimental httpclient code. it has web socket example, server + cmd client. https://github.com/fafhrd91/httpclient On Feb 25, 2013, at 4:12 PM, Andrew Barnert <abarnert@yahoo.com> wrote:
On Feb 25, 2013, at 16:41, Nikolay Kim <fafhrd91@gmail.com> wrote:
You can check my experimental httpclient code. it has web socket example, server + cmd client.
How does that answer my request? The whole point was to show how passing information between socket handlers (or, more generally, coro chains) is easier with tulip than with traditional async solutions. An http client doesn't do that. (And it's probably much more complex, too.)
Also, I had some troubles figuring out how to run tests because setup.py doesn't actually install Tulip and "import tulip" can be used only from within the root directory.
I'm planing to work on udp support sometime next week. i'll implement echo examples except udp, later today.
Thanks. --- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ http://code.google.com/p/pysendfile/
Personally I think you'd be crazy to install this version of tulip (it's not beta, it's way before alpha!). The setup.py file only exists to build the C extension for Windows. (How to run tests is explained in README BTW. There is no boilerplate there. :-)
Sorry for the top post, but I'm on a phone. I'd love to see a trivial chat server in the demos. There are many designs for async servers that work great with echo and even http but fall down with chat (because of interactions between clients), and it would be very useful to see how tulip makes it easy to do it right. Sent from a random iPhone. On Feb 22, 2013, at 13:17, Guido van Rossum <guido@python.org> wrote:
You can check my experimental httpclient code. it has web socket example, server + cmd client. https://github.com/fafhrd91/httpclient On Feb 25, 2013, at 4:12 PM, Andrew Barnert <abarnert@yahoo.com> wrote:
On Feb 25, 2013, at 16:41, Nikolay Kim <fafhrd91@gmail.com> wrote:
You can check my experimental httpclient code. it has web socket example, server + cmd client.
How does that answer my request? The whole point was to show how passing information between socket handlers (or, more generally, coro chains) is easier with tulip than with traditional async solutions. An http client doesn't do that. (And it's probably much more complex, too.)
participants (4)
-
Andrew Barnert -
Giampaolo Rodolà -
Guido van Rossum -
Nikolay Kim