Hi Jochen,

in my opinion, reusing the soft locking support (both on client and server 
sides) for DMS and Data would not be so straightforward, as the it was 
essentially designed for web pages. The basic idea behind it is very simple: 
when an editor opens a page in author mode, the page adds her to a list of 
users currently editing the same page and then starts polling the server at 
regular intervals to update this list as well as checking if the page was 
recently saved by one of the current editors and warn everybody else about it. 
Sure, that could be adapted to your use case but would definitely need some 
overhauling. 

HTH,

Federico


On Feb 16, 2011, at 5:47 PM, Jochen Fliedner wrote:

> 
> Hi Federico,
> 
> many thanks for the info! 
> Maybe i could check to leverage some lower level support for the soft 
> locking/ui feedback from the module - in the case we consider a license. In 
> data or dms module the check may be much less granular and the ui for this 
> can be very basic, for example a js-alert and no display of the dialog for 
> data item or document may do it. Given your (or the other developers) 
> knowledge of the module code, do you guys consider this approach feasible? 
> 
> Regards
> j 
> 
> 
> 
>> -----Original Message-----
>> From: [email protected] [mailto:user-list-owner@magnolia-
>> cms.com] On Behalf Of Federico Grilli
>> Sent: Wednesday, February 16, 2011 4:28 PM
>> To: Magnolia User-List
>> Subject: Re: soft locking module ui support for dms and data module
>> (was: RE: [magnolia-user] Node or page locking in CE vs. EE)
>> 
>> 
>> Hi Jochen,
>> 
>> soft locking currently only supports web pages, i.e. it gives an editor
>> working in authoring mode on a given page visual feedback regarding
>> other users currently editing and/or saving the same page.
>> 
>> Federico
>> 
>> On Feb 16, 2011, at 2:56 PM, Jochen Fliedner wrote:
>> 
>>> 
>>> Hi Gregory and list,
>>> 
>>> thanks for the info. In my concept i am now considering to use the ee
>> module as of http://www.magnolia-cms.com/magnolia-cms/magnolia-4-4/soft-
>> locking.html
>>> 
>>> In fact I am researching a solution that will be implemented as a
>> module that builds upon the admin interface and has nothing to do with
>> wcms templating. There will be no website repo involved, there are now
>> pages or paragraphs. The module will use approaches of data and/or dms
>> module or even leverage one of these modules by overriding
>> configurations etc. . We would rather call it a usage of magnolia admin
>> interface as a generic jcr ui with whatever bells and jingles.
>>> Regarding this for me now is important to know if the soft locking
>> module supports dms and data module in a similar way, that is giving ui
>> feedback. Does anyone know?
>>> 
>>> Regards
>>> j
>>> 
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: [email protected] [mailto:user-list-
>> owner@magnolia-
>>>> cms.com] On Behalf Of Grégory Joseph
>>>> Sent: Monday, February 14, 2011 10:47 PM
>>>> To: Magnolia User-List
>>>> Subject: Re: [magnolia-user] Node or page locking in CE vs. EE
>>>> 
>>>> 
>>>> Hi Jochen,
>>>> 
>>>> Yes, the Soft Locking module is currently an Enterprise Edition
>> module.
>>>> http://documentation.magnolia-cms.com/releases/4-4.html
>>>> 
>>>> I'd have to dig back in the code for details, but I think there is so
>>>> form of locking in core (i.e in all editions) to prevent concurrent
>>>> saves of nodes, however this gives no feedback to the user and can
>> thus
>>>> result in overwritten content.
>>>> 
>>>> -g
>>>> 
>>>> On 14 Feb 2011, at 19:40, Jochen Fliedner wrote:
>>>> 
>>>>> 
>>>>> 
>>>>> Hi list,
>>>>> 
>>>>> regarding 4.4 sometimes it was mentioned that there was a planned
>>>> "basic locking approach".
>>>>> Did this result only in the Jira component/the module
>>>> http://jira.magnolia-cms.com/browse/MGNLSLOCK that is targeted to the
>>>> ee?
>>>>> Or is there actually any kind of "hardlocking" or warning mechanism
>> in
>>>> ce - maybe even in an older version, and I did not realize that yet?
>>>>> 
>>>>> Regards
>>>>> jf
>>>>> 
>>>>> 
>>>>> --
>>>>> pro!vision GmbH
>>>>> Löwengasse 27 A
>>>>> 60385 Frankfurt am Main
>>>>> Telefon +49 (69) 87 00 328-13
>>>>> mailto:[email protected]
>>>>> http://www.pro-vision.de
>>>>> 
>>>>> Geschäftsführer: Karim Khan, Stefan Seifert
>>>>> Sitz der Gesellschaft: Berlin
>>>>> AG Charlottenburg, HRB78141, USt-IdNr. DE209954974
>>>>> 
>>>>> 
>>>>> 
>>>>> ----------------------------------------------------------------
>>>>> For list details see
>>>>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>>>>> To unsubscribe, E-mail to: <[email protected]>
>>>>> ----------------------------------------------------------------
>>>> 
>>>> 
>>>> 
>>>> ----------------------------------------------------------------
>>>> For list details see
>>>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>>>> To unsubscribe, E-mail to: <[email protected]>
>>>> ----------------------------------------------------------------
>>> 
>>> 
>>> 
>>> ----------------------------------------------------------------
>>> For list details see
>>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>>> To unsubscribe, E-mail to: <[email protected]>
>>> ----------------------------------------------------------------
>>> 
>> 
>> 
>> 
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <[email protected]>
>> ----------------------------------------------------------------
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> 



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to