Cause this way, doing operations by multiple users is impossible, as the class is singleton.

CommentFileSizeAuthor
0001-engine-do-not-pre-store-the-userId-as-maestro-class-.patch1.05 KBaron novak

Comments

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Needs review » Needs work

This one needs work, the current patch breaks the things as the getter is not invoked. The base class has to be modified as well, i have the code, i just need to forge a patch.

_randy’s picture

_randy commented

You're right -- there is an assumption of who it is we're latching on to in the engine.
I will have to double check, but can't we just directly set the user ID in a new method of setUserID? The default would be current user. I suppose the constructor of Maestro could also be used to set the desired UID.