I posted a similar message on this topic yesterday... the Mere Mortals framework includes a class called "mmUserManager" that appears to be used to authenticate and retain the id of a logged-in user. However, this doesn't appear to work in a Web application. The problem is that it doesn't appear that mmUserManager is implemented in a "session-specific" manner. The upshot is this - if my web app tries to get the "UserID" property from mmUserManger, it will always be the id of the last user who logged on, not the id of the current user, because mmUserManager appears to be shared by all sessions. This is a problem.

I've gotten advice suggesting I implement some behavior to store the user id in the session, but this will require some pretty extensive architectrue changes. If there's some possibility of keeping an instance of mmUserManager in memory on a per-session basis, it would save me a lot of work.

Is there a way to make the mmUserManager class somehow session-specific?