Bernd Fondermann wrote:
Fellow researchers,
Should we hold roster instances in memory per Session or per User?
In the first case, we could add methods like get/setAttribute(String,
Object) to SessionContext like this:
sessionContext.setAttribute("roster", roster);
After thinking more carefully about it, I think it's best to not hold a
roster instance in the session. Accessing the full roster is rarely
needed on the server. And modifying the roster is possible from another
session, too. So overall it would not be a good idea.
I'd propose having a RosterManager providing all roster operations like
+ retrieving the roster
+ adding contacts
+ modifying contacts
etc.
WDYT?
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
