[protege-discussion] Versioning in Client Server Mode

[Jonathan Carter]

Thanks Tania,

That would be good. I appreciate that the revert is not a straight- 
forward use-case in client/server mode and I agree with what you're  
suggesting. The revert needs to be a controlled and co-ordinated  
thing. Thinking about it due to that is there a case for saying that  
you can archive in client/server mode but only revert in stand-alone  
mode? I know it's not as slick or complete but it forces you to  
quiesce the server (stop it, basically) before you do any revert from  
an archive.
This is basically how I operate my 'super-user' privileges currently -  
only super users access the project in stand-alone mode. This  also  
works well when making things like Form changes.

Jonathan

__________________________________________
Jonathan Carter - Head of Technical Architecture
Enterprise Architecture Solutions Ltd


On 18 Apr 2008, at 01:44, Tania Tudorache wrote:

> Kristina, Jonathan,
>
> Currently, there is no support for archive/revert in client-server  
> mode.
> It is not clear what these functions should do in a multi-user  
> setting.
>
> For instance, the archive could take place either on the server or on
> the client. From the implementation point of view, it is easier to  
> make
> it on the server. This would impact the performance of the server,  
> while
> the archive is being done. However, the bigger problem is the revert
> operation. Imagine how unhappy the other online users would be if at
> some point you would revert the ontology to a previous version and all
> their changes would disappear. Revert should probably be controlled  
> by a
> policy that would allow only some privileged users to do the  
> operation.
>
> I've added an enhancement request for supporting the archive/revert in
> multi-user mode. Probably we'll be able to implement the archive on  
> the
> server pretty easily, but the revert will require more work:
>
> https://bmir-gforge.stanford.edu/gf/project/protege3owl/tracker/?action=TrackerItemEdit&tracker_item_id=314
>
> Tania
>
>
>
> Jonathan Carter wrote:
>> That's an interesting question. I'd like to know what the options for
>> doing this are, too.
>>
>> Currently, I am stopping the server, loading the project in
>> stand-alone mode and archiving it that way.
>>
>> __________________________________________
>> Jonathan Carter - Head of Technical Architecture
>> Enterprise Architecture Solutions Ltd
>>
>>
>> On 17 Apr 2008, at 13:45, KristinaN at gmx.net  
>> <mailto:KristinaN at gmx.net>
>> wrote:
>>> Hallo!
>>>
>>> I can't use the "archive current version" button when I'm working  
>>> with
>>> Protege in Client-Server-Mode. Can I do anything so that the clients
>>> can use versioning?
>>>
>>> Thanks for any help!
>>>
>>> Kristina
>>> -- 
>>> Psssst! Schon vom neuen GMX MultiMessenger gehört?
>>> Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion at lists.stanford.edu
>>> <mailto:protege-discussion at lists.stanford.edu>
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:
>>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
>>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20080418/04d642f1/attachment.html>