Hi all, IMO, the current behavior is ok because inviting to an application is followed by an email and we can mention to login in and check.
But if above is really an issue we need to attend, we should be able to use guaranteed delivery messages to send the new event about new application and update the applications in session. thank you. On Thu, Mar 12, 2015 at 2:13 PM, Gayan Dhanushka <[email protected]> wrote: > Hi all, > > Let's look at a simple scenario. > > User A and User B logs into AF. User A creates an application and invite > user B into that application. Currently until user B logs out and login, he > does not see the application. This is due to keeping user's application > information in the session. The application information in the session is > updated only when the user logs in. > > One thing that can be done is we can have a back end cache to track the > users who are invited to an application and during the user home page load, > a back end check can be done to check the cache and update the user home by > reloading the application list. > > But this may introduce a overhead to the user home page. > > WDYT ? > > Regards > Gayan > > -- > Gayan Dhanuska > Software Engineer > http://wso2.com/ > Lean Enterprise Middleware > > Mobile > 071 666 2327 > > Office > Tel : 94 11 214 5345 > Fax : 94 11 214 5300 > > Twitter : https://twitter.com/gayanlggd > -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
