We should make the parameter ice.billing_s3bucketregion optionnal, as it is only required for region with v4 authentication.

Moreover this will make v1.1.2 backward compatible.

IceGrid uses Ice::Service::print to print the registry/node usage and the ready message for nodes (enabled with IceGrid.Node.PrintServersReady). It would be better to output these on the console output instead like for the object adapter ready message (it's using consoleOut from IceUtilInternal).

It should support IceDiscovery like other graphical demo client.

Hi all.

When reading the Rationale for MongooseICE: "Many modern applications (mobile and web) are media intensive like those involving audio, video, gaming, and file transfer. MongooseICE helps to get communication done peer-to-peer (without going through a server) so your bandwidth and server-side costs don't need to be as much of a concern."
That's fantastic. And I get so excited for being

Summary

Other tools like go-stun can print the type of NAT detected by the STUN server:

> go-stun
NAT Type: Full cone NAT
External IP Family: 1
External IP: 166.111.4.100
External Port: 23009

t would be convenient if our stun did this too, and printed the result to the info log. That way people could include it in issue descriptions

@hugoArregui

This might not be needed, but would be nice to add some basic tests for this (n time should select this pair etc...)

Just a few checks to make sure we don't take relay when we have good host candidates etc..