.Net Messaging system - meta and data adapter linking

[wwatts]

Thanks Alessandro.

As a follow-up, we have a situation where there are multiple sites each wanting data associated with there site. For example all users at Site A should only see Site A data. The Site A data is a subset of a larger group of data which simply means that it is filtered by adapter code. Given that scenario, is it better to have

1. A adapter set for the larger superset of data with adapters for each Site specific data where it can be filtered.
2. A single adapter where each site subscribes to a specific table within the adapter.

It should also be noted that there are multiple data types going to each site e.g.:

Data Type 1: Site A Data Type 1, Site B Data Type 1...
Data Type 2: Site A Data Type 2, Site B Data Type 2...
...

Just trying to understand the best subscription policy that provides the best performance.

Thanks in advance.

[DarioCrivelli]

For what concerns the Server, there are no performance differences related with the way different items are supplied.
By resuming, there are 3 ways to do this.

0. Different Adapter Sets for different sites.
1. Different Data Adapters for different sites, belonging to a common Adapter Set.
2. Different items for different sites, all of them supplied by the same Data Adapter.

You could choose based on your convenience. For instance, as you use Remote .NET Data Adapters, using multiple Data Adapters allows you to place different Remote Servers on different hosts.

Just consider that option 1 has a limitation in authorization management.
In fact, the specific Data Adapter to which the items are requested is not notified to the Metadata Adapter. This is because the multiple Data Adapter feature was introduced recently and we preferred not to extensively modify the Metadata Adapter interface. As a consequence, you cannot prevent a client from one site from asking items from a different site, unless you differentiate the item names too (which would make option 1 similar to option 2).