-
November 7th, 2017, 03:43 PM
#2
I'm not sure I understand all your requirements, but it seems to me that they can be reduced to the following functionalities:
- Request-reply interaction with the Client.
- Responses which depend on the user identity.
These behaviors are not directly provided, but can be mapped onto the item-based publish-subscribe interaction.
For request-reply , our suggestions are provided in this post.
For user-specific responses, you can define different items, one for each user, to be properly handled by the Data Adapter.
Obviously, each user must subscribe to its own item, but this can be enforced by the Metadata Adapter.
In fact, in getItems, you can map client-side item names to Data-Adapter-side item names; for instance, a user U1 can subscribe to "myItem" and getItems will decorate it to become myItemU1 (at the same time, it will prevent any client from subscribing to myItemU1 directly).
This technique can also be mixed in a request-reply scenario.
Similar Threads
-
By santhosh in forum Client SDKs
Replies: 1
Last Post: September 23rd, 2013, 10:07 AM
-
By DarioCrivelli in forum General
Replies: 0
Last Post: June 13th, 2011, 03:50 PM
-
By sachinpatel2 in forum Client SDKs
Replies: 1
Last Post: March 25th, 2010, 09:04 AM
-
By DarioCrivelli in forum General
Replies: 2
Last Post: August 21st, 2007, 01:16 PM
-
By rsouissi in forum Adapter SDKs
Replies: 5
Last Post: December 13th, 2006, 08:42 AM
Tags for this Thread
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 12:09 PM.
Bookmarks