Tracking HttpEndpoint creation

[bronsh]

Hi
I would like to add the ability of tracking the creation of Http listener (after calling MetricsConfig.WithHttpEndpoint).
This will enable me to wait until endpoint is listening before proceeding with my process.

I would like to create a pull request, but I don't know what is the preferred way to do this.

I can think about 3 different options:

1. MetricsConfig will expose a copy of its private httpEndpoints dictionary. This will enable external users to use this dictionary to track their listener's task.
2. Add an overload to the method WithHttpEndpoint with an "out" parameter which returns the listener Task
3. Add a non-chainable method (StartHttpEndpoint) which returns a Task (instead of returning "this")

Please advise which option I should go with, or if you have some better idea.
Thanks !

[bronsh]

Hi
Please share your opinion about this issue
Thanks

[PaulParau]

Hi,

I think a cleaner way would be to add a boolean parameter to the WithHttpEndpoint method (something like bool waitUntilStarted = false). If it is set to true, then the method will not return this until the endpoint task has finished; otherwise it will behave as it does now.

What do you think of this solution?

Also, I'm curios, what use-case do you have that requires you to wait until the endpoint is listening?

Thanks

[bronsh]

I think returning a Task is a better option, because it lets you do other things while listener is starting, and still be able to track over the Task to know whether it succeeded in listening or not.

The use-case is an application which needs to fail if the http listening did not succeed, for example, if it doesn't have the permissions to listen on the specific port.
I want the user will know something went wrong. I don't want him to work with the application unless he fixes the problem.