Nikolay Kim

sockjs is just transport layer, it does not implement concept of rooms and subscriptions (at least it was like that when i developed pyramid_sockjs) so rooms and subscriptions are application...

I think this could solved by introducing `ToPyTuple` trait. `call` and `call_method` could use explicit ToPyTuple instead of generic ToPyObject. `()` could be resolved to `py.None()` in case of `ToPyObject`...

1. just added properties in this PR #101 2. default values are defined like this: ```rust def write(&self, data: PyBytes, request_counter: u32 = 0) -> PyResult { } def write(&self,...

technically awaitable object is just iterator. specifically for asyncio, iterator should return `asyncio.Future` object or result. I am working on asyncio event loop based on tokio framework https://github.com/fafhrd91/async-tokio network does...

oh, forgot to update deps. my repo should be fixed now. you need #98 pr. from c-level perspective awaitable is just iterator that return something "awaitable", in case of asyncio...

could [process priority](https://github.com/errantmind/faf/blob/aae75a54637bcf0e225e1078693d5110e444f7d5/src/epoll.rs#L47) affect throughput?

We can reuse predicates for middlewares. PR is welcome

if anyone interested, it should be possible in 1.0, resources and scopes are implemented generically in actix-web 1.0, so route group could be custom service with router. PR is welcomed.

i think this is right approach

@jdosornio you can do something like: ```rust App::new().service( web::scope("/prefix").service( web::resource("").to(..))) // handler for: /prefix ``` is that what you asking?