[Osr-101] Re: [Remark] Re: [Phoenix] checkin & checkout on the demo page

[Thomas Comiotto]

Hi Michi

I crosspost to osr-101 because that's the wrong list to discuss this.


>> Checkout means (open + lock)
>
>
> I think it's rather "lock + open" (and "save and unlock")
>

Consider stand alone clients. You might want to open and see what 
you're about to edit before you decide to request a lock.


>> but that will ususally be issued after already having opened a 
>> document (so why to issue another open?
>
>
>
> what do you mean by "another open"?

See above.

>
>> ). LOCK would be enough. Checkin means (save + unlock) but without a 
>> seperate save method provided you only have a single attempt to store 
>> your local changes on the server. UNLOCK would suffice.
>
>
> "save and unlock" could be translated to "exit/close" and "save" is 
> save but without unlocking. Makes sense?
>

We're talking about the url commands set by the server. Exit & close 
relate to the client's GUI. Killing a session by issuing a logout is 
all that's needed by the server.


> Another reason why we introduced the combinations/shortcuts is because 
> probably many servers provide these combinations
> out of the box instead of having to send two requests.

Give an example please. Might make sense with regard to repositories 
that support a copy -> modify -> merge -> commit model as for instance 
svn does, but not with systems that support exclusive locks I think. 
Fact is, currently you're forced to fire two requests because of the 
shortcuts (btw no lock/unlock derictives are defined in the specs so 
"shortcut" is not that appropriate of a term, is it?) as pointed out 
above.

Let's at least add <lock> and <unlock> directives to the spec!


>
>>
>> It's the client side application's job to glue the command urls 
>> together. A regular editing session can be considered as follows:
>>
>>  1. User opens a document
>>  2. User starts editing (Application asks if user wants to lock)
>
>
> you mean as soon as the user clicks into the opened document?
>

Yes.


--
Bests
Thomas


> Thanks
>
> Michi
>
>>  3. User edits
>>  4. Uuser might want to save
>>  5. User wants to close the document (Application asks if user wants 
>> to save + release lock)
>>
>>
>> Thomas
>>
>>
>>> Thomas
>>>
>>>
>>>
>>>> WDYT?
>>>>
>>>> Michi
>>>>
>>>>>
>>>>> -- 
>>>>> Bests
>>>>> Thomas
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Phoenix mailing list
>>>>> Phoenix at wyona.org
>>>>> http://wyona.com/cgi-bin/mailman/listinfo/phoenix
>>>>>
>>>>
>>>>
>>>> -- 
>>>> Michael Wechner
>>>> Wyona      -   Open Source Content Management   -    Apache Lenya
>>>> http://www.wyona.com                      http://lenya.apache.org
>>>> michael.wechner at wyona.com                        michi at apache.org
>>>> +41 44 272 91 61
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Phoenix mailing list
>>> Phoenix at wyona.org
>>> http://wyona.com/cgi-bin/mailman/listinfo/phoenix
>>>
>>
>>
>
>
> -- 
> Michael Wechner
> Wyona      -   Open Source Content Management   -    Apache Lenya
> http://www.wyona.com                      http://lenya.apache.org
> michael.wechner at wyona.com                        michi at apache.org
> +41 44 272 91 61
>
>