-
October 3rd, 2017, 10:04 AM
#4
Hi, there was a misunderstanding.
When I suggested "you should instead just throw a ConflictingSessionException" and "At this stage, you shouldn't do anything else and leave the "sessions" and "userinfo" maps unchanged" I meant something like this:
assert (! sessions.containsKey(sessionID));
if (userinfo.containsKey(user)) {
throw new ConflictingSessionException(-8, "Previous session termination", null, userinfo.get(user));
} else {
userinfo.put(user, sessionID);
sessions.put(sessionID, sessionInfo);
}
Then you should rely on the Server to call notifySessionClose and a new notifyNewSession to your Adapter.
Also ensure that your implementation of notifySessionClose undoes exactly all that was done in notifyNewSession, which means removing the session line from both the "userinfo" and the "sessions" Map.
Similar Threads
-
Replies: 0
Last Post: September 24th, 2022, 12:52 PM
-
By rvkvino in forum General
Replies: 1
Last Post: February 24th, 2017, 10:06 AM
-
By rvkvino in forum General
Replies: 3
Last Post: September 25th, 2013, 09:20 AM
-
By pradeepgamage in forum Adapter SDKs
Replies: 7
Last Post: May 17th, 2012, 09:21 AM
-
By mnenchev in forum General
Replies: 5
Last Post: September 8th, 2009, 03:07 PM
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 05:50 AM.
Bookmarks