{"action":"created","issue":{"url":"https://api.github.com/repos/thunderpush/thunderpush/issues/42","labels_url":"https://api.github.com/repos/thunderpush/thunderpush/issues/42/labels{/name}","comments_url":"https://api.github.com/repos/thunderpush/thunderpush/issues/42/comments","events_url":"https://api.github.com/repos/thunderpush/thunderpush/issues/42/events","html_url":"https://github.com/thunderpush/thunderpush/issues/42","id":85561741,"number":42,"title":"Can it be deployed in multiple Tornado Processes?","user":{"login":"danigosa","id":1827475,"avatar_url":"https://avatars.githubusercontent.com/u/1827475?v=3","gravatar_id":"","url":"https://api.github.com/users/danigosa","html_url":"https://github.com/danigosa","followers_url":"https://api.github.com/users/danigosa/followers","following_url":"https://api.github.com/users/danigosa/following{/other_user}","gists_url":"https://api.github.com/users/danigosa/gists{/gist_id}","starred_url":"https://api.github.com/users/danigosa/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danigosa/subscriptions","organizations_url":"https://api.github.com/users/danigosa/orgs","repos_url":"https://api.github.com/users/danigosa/repos","events_url":"https://api.github.com/users/danigosa/events{/privacy}","received_events_url":"https://api.github.com/users/danigosa/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-05T15:39:49Z","updated_at":"2015-08-13T12:31:14Z","closed_at":null,"body":"Can ThunderPus be deployed in several tornado processes and multiplex requests through Nginx? Or the Messenger registered by one Tornado process (and IOLoop) will not broadcast to others subscribed on a different process? I understand that it's not possible looking at the code, we're looking for a tornado push service but asking us if its possible to build a more flexible pusher that single-process one (and more scalable, indeed)."},"comment":{"url":"https://api.github.com/repos/thunderpush/thunderpush/issues/comments/130650710","html_url":"https://github.com/thunderpush/thunderpush/issues/42#issuecomment-130650710","issue_url":"https://api.github.com/repos/thunderpush/thunderpush/issues/42","id":130650710,"user":{"login":"kjagiello","id":74944,"avatar_url":"https://avatars.githubusercontent.com/u/74944?v=3","gravatar_id":"","url":"https://api.github.com/users/kjagiello","html_url":"https://github.com/kjagiello","followers_url":"https://api.github.com/users/kjagiello/followers","following_url":"https://api.github.com/users/kjagiello/following{/other_user}","gists_url":"https://api.github.com/users/kjagiello/gists{/gist_id}","starred_url":"https://api.github.com/users/kjagiello/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kjagiello/subscriptions","organizations_url":"https://api.github.com/users/kjagiello/orgs","repos_url":"https://api.github.com/users/kjagiello/repos","events_url":"https://api.github.com/users/kjagiello/events{/privacy}","received_events_url":"https://api.github.com/users/kjagiello/received_events","type":"User","site_admin":false},"created_at":"2015-08-13T12:31:14Z","updated_at":"2015-08-13T12:31:14Z","body":"No, it wouldn't work, unfortunately. We would need to change the core architecture a bit to make it possible. Ideally, you would want ability to spawn multiple API processes, that receive messages, send them to a routing service that keeps information about who is connected to which push-server and then dispatch the message to a specific push server. \r\n\r\nI've been planning to implement this for a while, but I would like to discuss a bit about other ways to crack this problem. My goal is to keep Thunderpush as simple as possible (avoid extra dependencies and so on), as it is now, but at the same time allow customisation for more advanced use cases like this one."}}