-
March 22nd, 2009, 02:45 AM
#1
Selectors and .NET
In the current version of Lighstreamer, are selectors supported for .NET? If not:
1. Is there are workaround?
2. Is this feature planed for a future release and if so when is the expected release?
Thanks
-
March 23rd, 2009, 10:31 AM
#2
Selectors are not yet supported through ARI (Adapter Remoting Infrastructure), on which remote .NET Adapter are based. They will be supported in the next major release, which is not expected in the short term.
Consider in any case that selectors should be used only in very specific cases, as they are heavy and are not really necessary. The best approach is to use personal items for each user. Also, Lightstreamer should be used to provide real-time data only, while historical data should come through a normal web/application server.
-
March 23rd, 2009, 02:37 PM
#3
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.
-
March 24th, 2009, 09:13 AM
#4
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).
Similar Threads
-
By Alessandro in forum Adapter SDKs
Replies: 4
Last Post: October 24th, 2011, 09:33 AM
-
By churrusco in forum General
Replies: 4
Last Post: November 8th, 2010, 02:26 PM
-
By limeni in forum Adapter SDKs
Replies: 6
Last Post: February 6th, 2009, 08:58 AM
-
By eric.s in forum General
Replies: 3
Last Post: November 24th, 2008, 11:13 AM
-
By rekhender in forum Adapter SDKs
Replies: 5
Last Post: July 23rd, 2008, 09:34 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 07:57 AM.
Bookmarks