Phil, as author of this class, can you have a look at this issue? I want to move alt_connection_timeout_hook_ and connection_timeout_hook_ out of the ORB_Core_Static_Resources and into the ORB_Core. The OC selector has a static member making this hard todo. 

added blocks

OK, to make the *connection_timeout_hook_ non-static, the call stack to the initializer needs to be changed to pass a reference to the ORB core in question. It isn't clear how that will happen. 

I suppose the proper steps should be:
1. ORB initializer calls something on the OC_Endpoint_Factory passing in a reference to the ORB_Core. 
2. the OC_Endpoint_Factory creates a new instance of the optimized endpoint selector, which initializes the connection timeout hooks on the supplied ORB core. 

This means that ORB_Core::connection_timeout_hook() needs to be non-static, which seems to be your goal. 

Also, the Default_Endpoint_Selector_Factory needs to be modified to also create a new endpoint selector instance for each ORB, presumably the ORB Core will call get_selector() once and take ownership of the supplied selector.

Back to the point of the bug, there's no intrinsic reason for the connection timneout hook to be static, it was actually a chore to make it work that way.

Let me know if you need me to do something else with this.

I ran into a few small issues because the OC one has a static member to store a value. 

Do you maybe have some time to have a look at this and try to get this non-static? It would remove the implicit service config/gestalt behaviour, making things more clear.

Johnny,

I went back and reviewed a little further.  The Optimized_Connection_Endpoint_Selector hook is static because it is necessary to match the signature needed by ORB_Core::connection_timeout method.

The Optimized_Connection_Endpoint_Selector really serves two distinct roles:
 - Provide an alternate means to set the connection timeout rather than loading the messaging library, and
 - Provide an alternate strategy for selecting endpoints at connection time.

The first role is filled with the static timout hook. If you want that to be non-static, you need to first decide how to reimplement the connection_timeout_hook mechanism in the ORB Core so that it takes a non-static pointer, or whatever. Once the hook is set, never again is the service configurator invoked.

The second role is that of the per-invocation endpoint selector. That is where the service configurator is involved, and there is where you can stash a per-orb  reference to the actual endpoint selector so as to avoid going through the service configurator on the critical path. You can even alter the endpoint selector factory so that it returns a private endpoint selector wholly owned by the calling ORB. I don't believe the connection timeout hook's staticness has any bearing on the removal of the service configurator access from the critical path. 

Take a look also at tao/Messaging/Connection_Timeout_Policy_i.*, there you will see a similar implementation for a static connection timeout hook. If you are reimplementing the connection_timeout mechanism in the ORB core, this will need to be modified also.