You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Jukka Zitting <ju...@gmail.com> on 2012/03/30 16:13:07 UTC

Only one workspace (Was: Handling namespace mapppings)

Hi,

On Fri, Mar 30, 2012 at 3:03 PM, Angela Schreiber <an...@adobe.com> wrote:
> i am not asking for having synchronized copies. you got that wrong.

ACK, my mistake.

> well, here comes our disagreement. imo a session on oak-jcr would
> never see the complete repository as it is bound to a workspace.
> the information what is exposed by that workspace is the responsibility
> of oak-core and that's basically also the reason why i had the
> login-method that contained a workspace name.

I see your point. My main worry here is that without exposing the
entire repository tree (i.e. containing all workspaces plus the system
subtree) directly through the Oak API, we need to come up with a lot
of custom methods for handling cross-workspace operations that could
just as easily be expressed as content updates.

Anyway, to avoid getting stuck on this point, here's a somewhat
radical suggestion:

    Let's drop trying to support more than one workspace for now!

Practically all our use cases require just a single default workspace,
so we'll be able to cover most of our goals without worrying about
extra workspaces and the login/user management/jcr:system mapping/etc.
complexities they bring to the table.

Once we have the basics in place, we can return to the question of
workspace support say in the Oak 0.5 - 0.7 timescale (just a rough
estimate), at which point it should still be fairly straightforward to
implement.

WDYT?

BR,

Jukka Zitting

Re: Only one workspace (Was: Handling namespace mapppings)

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Fri, Mar 30, 2012 at 5:53 PM, Thomas Mueller <mu...@adobe.com> wrote:
>>Let's drop trying to support more than one workspace for now!
>
> Would that mean, don't support multiple workspaces in the whole oak-core
> *API* for now? Or just don't support multiple workspaces in the
> *implementation* for now (and don't test with multiple workspaces)?

Both.

There's a quite a range of workspace management and cross-workspace
operations that we wouldn't need to include in the API just yet.

Existing things like passing the workspace name in the login() call
I'd just leave as-is and simply not use that functionality for now
until we have better consensus on how to proceed.

BR,

Jukka Zitting

Re: Only one workspace (Was: Handling namespace mapppings)

Posted by Michael Marth <mm...@adobe.com>.
+1 on ignoring now and revisiting later

> 
> 
> On 30.3.12 15:13, Jukka Zitting wrote:
>> Anyway, to avoid getting stuck on this point, here's a somewhat
>> radical suggestion:
>> 
>>     Let's drop trying to support more than one workspace for now!
> 
> +1 Good idea!
> 
> Michael
> 
>> 
>> Practically all our use cases require just a single default workspace,
>> so we'll be able to cover most of our goals without worrying about
>> extra workspaces and the login/user management/jcr:system mapping/etc.
>> complexities they bring to the table.
>> 
>> Once we have the basics in place, we can return to the question of
>> workspace support say in the Oak 0.5 - 0.7 timescale (just a rough
>> estimate), at which point it should still be fairly straightforward to
>> implement.
>> 
>> WDYT?
>> 
>> BR,
>> 
>> Jukka Zitting


Re: Only one workspace (Was: Handling namespace mapppings)

Posted by Thomas Mueller <mu...@adobe.com>.
Hi,

>Let's drop trying to support more than one workspace for now!

Would that mean, don't support multiple workspaces in the whole oak-core
*API* for now? Or just don't support multiple workspaces in the
*implementation* for now (and don't test with multiple workspaces)?

Regards,
Thomas




Re: Only one workspace (Was: Handling namespace mapppings)

Posted by Michael Dürig <md...@apache.org>.

On 30.3.12 15:13, Jukka Zitting wrote:
> Anyway, to avoid getting stuck on this point, here's a somewhat
> radical suggestion:
>
>      Let's drop trying to support more than one workspace for now!

+1 Good idea!

Michael

>
> Practically all our use cases require just a single default workspace,
> so we'll be able to cover most of our goals without worrying about
> extra workspaces and the login/user management/jcr:system mapping/etc.
> complexities they bring to the table.
>
> Once we have the basics in place, we can return to the question of
> workspace support say in the Oak 0.5 - 0.7 timescale (just a rough
> estimate), at which point it should still be fairly straightforward to
> implement.
>
> WDYT?
>
> BR,
>
> Jukka Zitting

Re: Only one workspace (Was: Handling namespace mapppings)

Posted by Angela Schreiber <an...@adobe.com>.
hi jukka

that sound like a pragmatic approach for the time being.
fine with me.

kind regards
angela

> Anyway, to avoid getting stuck on this point, here's a somewhat
> radical suggestion:
>
>      Let's drop trying to support more than one workspace for now!
>
> Practically all our use cases require just a single default workspace,
> so we'll be able to cover most of our goals without worrying about
> extra workspaces and the login/user management/jcr:system mapping/etc.
> complexities they bring to the table.
>
> Once we have the basics in place, we can return to the question of
> workspace support say in the Oak 0.5 - 0.7 timescale (just a rough
> estimate), at which point it should still be fairly straightforward to
> implement.
>
> WDYT?
>
> BR,
>
> Jukka Zitting