3 ms·
This looks fantastic. Thanks for writing it. How would you go about restricting access to channels to a specific user or users? My first take would be to iss
by bham 17y ago
This looks fantastic. Thanks for writing it.
How would you go about restricting access to channels to a specific user or users? My first take would be to issue an unguessable id upon successful authentication and use this id as the channel id -- a shared secret. Only those who should know the id do know it.
I don't see support for streaming; the connection to the long-polling client is closed after consuming. Are you planning on adding support for streaming new messages as they are published?
- bham 17y agoI just had some time to scan your repository on GitHub and noticed this: http://github.com/slact/nginx_http_push_module/commit/6823f7080c29db22f5b3178631031179ee383142 http://github.com/slact/nginx_http_push_module/commit/6823f7... Though it just looks like a stub for now. Also, I read the following here: http://github.com/slact/nginx_http_push_module/issues/unreads#issue/20/comment/68601 http://github.com/slact/nginx_http_push_module/issues/unread... "Meanwhile, you can use your application to do the authenticating, and generate ids for already-authenticated clients from a large enough (> 2^128) keyspace for security." So, there, I did my homework.