-
February 22nd, 2008, 09:44 AM
#2
Some general architectural suggestions are available in this FAQ.
Unfortunately, no code examples are available.
However, consider that only the "notifyUser" method of the Metadata Adapter is involved in authentication. The other "notify" methods are related to authorization of specific actions (namely, opening of new sessions and subscriptions to items). For instance, by implementing "notifyNewSession" and "notifySessionClose", you can keep track of the number of sessions currently open for each user and block new sessions if some user related limit is reached.
Note that the "notifyUser" implementation can be blocking, but it should also collect any user authorization information available and cache it, so that the other authorization methods can be nonblocking.
Similar Threads
-
By Alessandro in forum Adapter SDKs
Replies: 4
Last Post: October 24th, 2011, 09:33 AM
-
By squint in forum Adapter SDKs
Replies: 1
Last Post: September 10th, 2010, 11:37 AM
-
By dalmy in forum Adapter SDKs
Replies: 1
Last Post: July 12th, 2010, 09:38 AM
-
By k0nan in forum Adapter SDKs
Replies: 1
Last Post: May 12th, 2010, 09:50 AM
-
By stephenlam in forum Client SDKs
Replies: 5
Last Post: April 22nd, 2010, 09:19 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 04:00 AM.
Bookmarks