David E Jones wrote:
That sounds pretty backwards Adrian, ie do the security changes and then do the execution context.

Actually, no. The ExecutionContext was first mentioned in the security redesign document. The multi-tenancy aspect was mentioned afterward.

My employer has no need for multi-tenancy. However, my employer could really use the new security design. So, I'm trying to get the new security design into the project in a way that is compatible with your multi-tenancy plans.

The changes I committed meet *those* goals. I don't see where my commits prevent you from implementing multi-tenancy. If your goal is to have code reference the delegator as an interface, then what's the problem? I did that for you. If you want to have the delegator interface in a different folder, then fine - move it there.

As I keep saying, it doesn't have to be "all or nothing." We can bring the concepts into the project a little at a time. I don't see the multi-tenancy thing being completed any time soon - there is far too much work to be done. In the meantime, why hold up the security redesign?

-Adrian

Reply via email to