In the end i took your advice and used session variables to store the key to pass to the entity manager in createdatasource. I added a layer of basic authentication to the odata feed which enabled me to catch the user logging in/requesting a page and using their credentials found the appropriate key for their database and stored it in a session variable. When the datasource was created I queried the session variables, got the key and set the datasource. Super!!

 

Thanks for your help

 

In OData, since we don't have any control over the client, you'll need to pass the extension into the EntityManager used by the OData service.  You can do this by overriding the CreateDataSource method in the OData service, so that you can then construct your EntityManager with the appropriate extension.  As for knowing that extension, you might pass it with the request, or retrieve it from a previously saved session variable.

 

 

I am currently in the process of extending my Silverlight application (which uses Devforce) to also include a simplifed HTML5/JQuery version. I noticed that it is quite simple to enable OData on the server side which I did and tested working fine, but now I have hit a problem which I do not know how to solve.

 

At the minute the silverlight app authenticates and after authentication uses a key specific to the user to identify what database to connect to. This key is passed into Devforce (as a KeyExtension) when creating the datasource which is used on the server side in a custom IDataSourceKeyResolver.