Carsten Ziegeler wrote > Carsten Ziegeler wrote >> I still have the feeling that mounting other workspaces into the >> resource tree is the easier way. >> With that we wouldn't need to change content loading, resource events >> and maybe other things to come? >> >> Can we go a step back please and see what use cases we really have? >> > With the authentication info and the new resource resolver factory, we > will have a mechanism to log in the user optionaly into resource providers. > So for example if the authentication info contains a specific key/value > pair, a login to a workspace resource provider which mounts workspace > xyz at /xyz could be done. If the key/value pair is missing, the login > to this resource provider is not successful and therefore in this > resource tree /xyz does not exist. > > If now the resource resolver is configured to search scripts in > /xyz/scripts, /apps, /libs everything should work. > > Just a rough idea. > Just as an additional rough idea, currently resource providers can overlay, for example we have the root provider mount the default workspace at /. However it is possible to mount lets say a file system at /libs/mystuff
Now, maybe a similar approach could be done with resource providers for other workspaces. So if you have copies of stuff in a different workspace and want user A to use these copies, then the content of this workspace could be layed over the default content in the resource tree. I think this should be double without too many problems. Carsten -- Carsten Ziegeler [email protected]
