Warning when making multiple connections from the same browser session

[RichP1]

Hi Alessandro, thanks for your response.

The problem we have is that our application contains some complex logic in the metadata adapters, which is adapter specific. So Adapter A can't be bundled with Adapter B as it requires a completely different metadata adapter.

As I understand it, the multiple adapter configuration groups adapters with a single metadata adapter. Is this the case and, if so, can you think of any other workarounds for our problem?

Thanks,

Richard

[Alessandro]

Richard,

The solution is to implement some simple switch logic in your Metadata Adapter. In other words, the Metadata Adapter is physically one, but based on the item names (thus, on the Data Adapter), it can delegate the actual logic to different classes.

Of course, the authentication logic should be independent of the Data Adapter. It's only the authorization logic that can be switched based in the Data Adapter.

Does this meet your needs?

Cheers

Alessandro

[RichP1]

We were hoping to avoid implementing a delegating Metadata adapter as it adds complexity, although it seems that might be the only way forward.

As a general question, why is it a problem to have multiple browser instances connecting to different data adapters as in our application? We notice that, when the user clicks 'Ok' on the alert box, the data streams correctly, so we're not entirely sure why the warning is shown.

Thanks,

Richard

[Alessandro]

Richard,

It all depends on the connection pool of the browser. Each browser process instance allows a maximum number of concurrent connections to the same host. In some cases this number is 2, in other cases it's larger.

If you launch independent browser instancesm the connection pool is not shared. But this applies to IE and not to Firefox (which creates one process instance only).

If you don't want to share your Lightstreamer connection (and Metadata Adapter) among multiple Data Adapters, a trick could be to use alias hostnames. In some cases, the browser just looks at the hostname and not at the IP address to allocate a connection pool.