Since your login process is not part of the Silverlight application, you might be able to use initParams to pass the server information to the SL application, which in turn would use this as its key extension when creating an EntityManager. 

 

If initParams won't work, then maybe use one extension-less EntityManager to ask (maybe via an RPC call) which server it should be using for the user, and then create an EntityManager with a key extension representing that server.

When creating the entity manager on the client side, I pass a Guid.NewGuid().ToString("N") as the extension key, forcing each silverlight app to have it's own key values in the map.

 

Works as expected now.

 

The environment is selected on the server side during the login process.  Silverlight app is initialized after this.  The extension key wouldn't be known when the EntityManager is created on the client side.  It's a catch 22.

 

Hence the need to be able to clear the map.

Currently, there isn't a way to reset the keys.

However, your use case seems like a perfect example to use DataSourceExtension. Basically you pass in your DataSourceExtension when you create your EntityManager, and in your IDataSourceKeyResolver.GetKey method, you just resolve different keys based on the extension passed in.

See http://drc.ideablade.com/xwiki/bin/view/Documentation/data-sources#HDynamicconnectionstrings for more details.

Hope this helps.

 

User logs out and the forms authentication login screen comes up as expected.

 

User logs in again, selecting a different server.  However, because the DataSourceKeyMap is static (and apparently, not clearable... we tried EntityManager.DataSourceResolver.DataSourceKeyMap.Clear(), didn't work), the only way the keys are reset is by closing the browser (ie, shutting down the app).

 

Shouldn't there be a way to reset the keys?