Re: So many hard-coded dropsonde destinations to metrons

Amit Kumar Gupta

Oddly, I can see your list on nabble here:

But it's just blank in the email, and also on the archive:

Here's the list for anyone else trying to read it:

10:// dropsonde.Initialize("localhost:3457", origins...)

175: "localhost:3457",
84: dropsondeDestination = "localhost:3457"
67: dropsondeDestination = "localhost:3457"
82: dropsondeDestination = "localhost:3457"
68: dropsondeDestination = "localhost:3457"
59: dropsondeDestination = "localhost:3457"
178: "localhost:3457",
109: dropsondeDestination = "localhost:3457"
53: dropsondeDestination = "localhost:3457"
120: dropsondeDestination = "localhost:3457"
166: dropsondeDestination = "localhost:3457"
91: dropsondeDestination = "localhost:3457"
65: "localhost:3457",
89: dropsondeDestination = "localhost:3457"
53: dropsondeDestination = "localhost:3457"
74: dropsondeDestination = "localhost:3457"

On Fri, Sep 4, 2015 at 3:34 AM, Noburou TANIGUCHI <dev(a)> wrote:

(This is a post in proxy of my collegue.)

There are so many hard-coded dropsonde destinations (actually each of them
is a metron's listening port) in multiple repositories, while metron's
listening port itself is configurable.

Below is the list that we've found it is hard-coded:

Are they going to be finally configurable in the near future, or is there
any reason to hard-code them?

Thanks in advance.

I'm not a ...
noburou taniguchi
View this message in context:
Sent from the CF Dev mailing list archive at

Join { to automatically receive all group messages.