Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Collaborative Work with File approach

Thanks, but at least some mire details information on the requirements themselves behind the purpose would be great.

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de DAUSSY Arthur
Envoyé : lundi 4 novembre 2013 14:52
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Collaborative Work with File approach

 

Hi Sebastien,

 

 Before explaining everything I have to make some tests. However the link with the control mode is that I would like to use it in order to create partitions of my model. Each part of this partition will be used to define what can be lock by a single user.

 I hope I will be able to give you more information soon.

 

Arthur Daussy

Atos

arthur.daussy@xxxxxxxx

+33 5 34 36 32 90

LogoAtosPapyrus

 

 

 

 

De : mdt-papyrus.dev-bounces@eclipse.org [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien 166342
Envoyé : lundi 4 novembre 2013 14:02
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Collaborative Work with File approach

 

Hi Arthur,

 

Please could you give more on information on what is the plan ? How does it fit with the “control” mode.

 

Thanks,

Best… Sébastien.

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : lundi 4 novembre 2013 13:59
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Collaborative Work with File approach

 

Hi, Arthur,

 

Indeed, there are more options (sadly! ;-) for collaboration than CDO.  Sounds good to me.

 

The only thing I would suggest is to ensure that any new APIs that address/identify/reference resources use URIs or something suitably generic.  There should be no new APIs that assume file/workspace storage unless they specifically address use cases that only make sense for files and workspace resources.  One never knows but that new functionality may "just work" on models in CDO, too.  Even controlled resources are now supported in CDO, so if your work elaborates on that, then the CDO integration may be able to benefit from it, too!  For example, if you plan to use SVN locks to reserve access to resources, this could be abstracted in such a way that it will be easy to plug in CDO locks instead for resources in that context.

 

Thanks for the heads-up!

 

Christian

 

 

On Nov 4, 2013, at 7:49 AM, DAUSSY Arthur <arthur.daussy@xxxxxxxx> wrote:



Hi All,

 

I would like to inform you that I will start working on a new feature. Although CDO is now a good way to do collaborative work, some of our clients still need to be able to do collaborative work on files.

This is why I going to work on a file approach for team working. A new branch adaussy/FileCollaborativeWork-420977 will be created to support this effort.

If you have any information on APIS for this king of operation please tell me.

 

Regards,

 

 

Arthur Daussy

Atos

+33 5 34 36 32 90

<image003.png>

 

 

 

 


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 


Back to the top