Timur Shemsedinov

Results 172 comments of Timur Shemsedinov

![thenablearray](https://cloud.githubusercontent.com/assets/4405297/24071856/8d8595c4-0be4-11e7-9a41-897899fe9321.png)

![projection](https://cloud.githubusercontent.com/assets/4405297/24072473/ee2e31d2-0bef-11e7-9498-25ea14780fdd.png)

@nechaido Such an approach would be good for PG based application, when all business logic, constraints and queries will be executed in PG. We use PG just for persistent storage...

@belochub not prioritized issue, now we can use one counter in db for all threads, so it it obvious bottleneck but it's as a temporary solution.

I see but do you need this feature for current project?

This PR should not contain commits not related to timeout.

You are doing good code but mixing multiple changes into one PR, we need to talk about process.

1. This example is not about front-end, it shows server-side platform and access to it from browser, so client-side optimizations are not a goal for us. Moreover we serve static...

Yes, you can make PR with this quick patch and issue to implement 'disconnect' event and example how to use this event with subscription.