Re: Locking on add container

[Benjamin . Papez]

Hi Serge,

sorry, my second statement in this thread is a bit confusing, as I talked about locks "after" adding. That was rubbish, I should have written, locks "while" adding.

The requirement in our application is that different users may add containers to the same container list at anytime. Now the AddContainer-Engine locks the container list, while it is open for one user. The second user gets a lock, until the first user ends his adding.

You said, that the reason is that users could modify raniking, while others add container. Wouldn't it be possible that you lock the container list and disallow adding only while somebody works in the ContainerListProperties-Engine to modify ranking and also vice versa - disable ranking, while somebody adds a container. We only would like to have that two users could add a container in the same container list simultaneously, just like two users can update containers in the same container list at the same time.

Greetings,
Benjamin Papez


Serge Huber <[EMAIL PROTECTED]> wrote on 08.10.2004 14:06:22:

>
> Hi Benjamin,
>
> Locking is really non-trivial, because it needs to also take into
> account clustering problems. We usually first start with big locks, and
> then try to see if there are ways to make them smaller.
>
> I'm not sure what you are refering to though. Maybe one of your users
> didn't close the window with the "Ok" or "Cancel" button ? Because it
> should work in that case. If the case where the user closes the window
> without giving some notification to the server (could happen if for
> example the user closes the window with the red cross on Windows XP),
> then the lock will stay active until it timeouts. And lock timeouts are
> configurable.
>
> Regards,
>   Serge Huber.
>
> [EMAIL PROTECTED] wrote:
>
> >
> > It would be understandable if you lock the container list while
> > somebody really opens the properties engine and actually does the
> > ranking, but now the container list is already locked after somebody
> > added a container into the list.
> >
> > We would like that different users should be able to create pages in a
> > container list but now the first user adds a new page and then nobody
> > is able to add his pages until the first users page is approved. Isn't
> > this too strict? Don't your customers have problems with that or is
> > there already a solution?
> >
> > Benjamin Papez
> >
> > Serge Huber <[EMAIL PROTECTED]> wrote on 28.07.2004 17:21:04:
> >
> > >
> > > Actually the reason this limitation exists is because it locks the
> > > parent container list, so that users can modify container ranking
> > > while other add container, which would have an undetermined consequence.
> > >
> > > Regards,
> > >   Serge Huber.
> > >
> > > At 13:36 28.07.2004, you wrote:
> >
> > > The lock-in/lock-out function in Jahia is used to avoid that two
> > > users modify the SAME content simultaneously.
> > >
> > > Unfortunately this does also mean that it is not possible that two
> > > users are adding NEW containers at the same time into the same
> > > container list. As soon as one selects to add a new container the
> > > lock is being set on the container list.
> > >
> > > Does it have to be that strict, that even the adding of new content
> > > is locked and not only the update or modification of content? Would
> > > it be possible to make the locking less strict for the case of adding?
> > >
> > > Benjamin Papez
> > >
> > > System Architect
> > > ***************************************************
> > > COMMARO mobile trading systems GmbH
> > > Kohldorfer Strasse 98
> > > A-9020 Klagenfurt - Austria/Europe
> > >
> > > phone: +43 (463) 298505-38
> > > fax: +43 (463) 298505-22
> > > ***************************************************
> > > - -- --- -----=[ serge.huber at jahia dot com ]=---- --- -- -
> > > Jahia : A collaborative source CMS and Portal Server
> > > www.jahia.org Community and product web site
> > > www.jahia.com Commercial services company
>
>