-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make udp optionals #36
Comments
Doing this is BC break, so I think this should be done before 2.0.0 release. |
I don't like to much enabling or disabling base services of the bundle, instead of enabling/disabling them. what if we make them lazy ? http://symfony.com/doc/current/components/dependency_injection/lazy_services.html |
Will take a look. |
This will be not useful at all, because connection definition require
So even if the services are lazy loaded, we will have useless So the only way is the way I described on my issue AFAIK. If you prefer to keep both udp and http services, then close the issue. |
It will be confusing if users make use of events. |
What do you mean by deny? I think the listener could simply ignore them. If you think it's too complex, so we can just leave it as is. |
Or the listener may trow an exception ... |
That's an idea. 👍 |
@Algatux Since #42, the http connection is required too. I think the http connection should always be provided, and the udp optional. This is basically the same way on the core library: https://github.com/influxdata/influxdb-php#writing-data-using-udp An http instance is create first, then you change the driver for the UDP one. |
Currently, both http and upd client/database instances are created, even if we don't needed.
Maybe we could make it optional with the config:
Both
udp
andhttp
port would befalse
by default and a configuration validation could check if at least one of them is enabled.Edit: Only udp will be optional: #36 (comment)
What do you think?
The text was updated successfully, but these errors were encountered: