Jürgen Hoffmann wrote:
Hi Shane,
Hi there. Thanks for replying!
How do you store the modifications the user has made? Within the Users temporary storage, or within a pull tool?
Actually, neither; I just added fields to the TurbineUser object itself. (This is a fairly simple webapp, and so I kept the schema simple, too.)
I realize that this is part of the problem, and mentioned in the previous message that one solution might be to "refactor TurbineUser to not have anything interesting in it."
However, this issue seems to be somewhat independent of my situation. For instance, consider where a user starts session X, starts session Y, changes his password in session Y, and leaves session X to expire. At that time, TorqueUserManager will then save the unchanged TurbineUser object from session X, and the password would revert to its original value, which I'm sure is a surprise to the user. And, of course, you can't just refactor the password out of the TurbineUser object. :)
I hope that clarifies things a bit. Shane --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
