alexeykupershtokh / nginx_push_stream_bundle Goto Github PK

Filters should know their own fields, e.g.:

• hash filter uses algo and secret
• prefix filter uses prefix

and act correspondingly if config is missing some of them.

Need an idea how to handle custom filter classes in this case.

NginxPushStreamBundle should write some logs if being supplied with a psr3 compatible logger.

Connection was a bad choice of the class name because it doesn't handle any connection but rather mainly allows to send some requests and generate links. The name 'Client' should fit better.

There are three options shoulbe supported

• id_generator: true (default value) - default id generator enabled. The %nginx_push_stream.id_generator.class% parameter value is used as a class name.
• id_generator: false to disable it
• id_generator: custom_service_name - to override it by a custom service.

Allow passing backtracks with channels in getSubUrls method. Backtracks should survive any filters including hash ones.

I don't like the current version of the Connection::send method:

https://github.com/QuickenLoans/uri-template is a good pretender