Enable the coexistence of a Server and Client sessions in the same process, which consume custom data types.

[mrsuciu]

The context of this change is the following:

If the application process is used to create a Server instance and also a Client session to a different server, than if custom data types have been initialized from the current Server instance, the Client session cannot decode the received custom types from the remote Server, due to the collision with the cloned existing ones from the current Server instance.
The type ids from the singleton GlobalFactory which in this case have already been set up by the local Server instance are copied and used instead.

The apparent working solution is to avoid the clone and create a new EncodeableFactory per CreateMessageContext that originates from a Client session.

[mregen]

Could you check if this line is root cause of the mixed up factory and if adding the true would help:

ServerBase.cs, line 1260
            // use the message context from the configuration to ensure the channels are using the same one.
            ServiceMessageContext messageContext = configuration.CreateMessageContext(`true`);
            messageContext.NamespaceUris = new NamespaceTable();
            MessageContext = messageContext;

Currently the server would use a reference to the global factory, after adding the types a client session would get all types from global factory too if the global factory is cloned. With the change a server would use a clone of global factory and types should not be shared.

[mrsuciu]

@mregen Yes this is a better solution and it works !!!

[mregen]

great, this should be less risk for regression..
although a little bigger memory footprint now server always use a clone of the factory.