On 3/17/10 4:31 AM, Bertrand Delacretaz wrote: > Hi, > > On Wed, Mar 17, 2010 at 2:45 AM, Justin Edelson <justinedel...@gmail.com> > wrote: >> Currently, although it's possible to log into different workspaces via >> AuthenticationInfo (even if httpauth and formauth don't support this); >> script resolution only happens against the default workspace. I don't >> see any reason for this restriction - it seems to me you should resolve >> scripts from the same workspace as the one resource was resolved from. >> WDYT?... > > In general yes, thought it might be interesting to fallback to another > workspace? This makes sense.
> Assuming you use workspaces for multi-homed websites, one could > imagine having a "generic scripts" workspace where the script > resolution would look after looking in the current resource's > workspace. I'm actually thinking almost the opposite - I clone a script from the default workspace and edit it in a private workspace. I need to be able to "preview" that modified script before pushing it back to the default workspace. Ironically, as things currently stand I can do this with regular resource resolution, but not script resolution. > That might complicate things and/or cause performance issues > though...just thinking that it might be a valid use case, so just > having hooks for that might be good enough for now. The only performance issue I see is that the workspace name needs to be part of the cache key, which makes the cache keys larger and the cache itself potentially larger. Justin > > -Bertrand
