<br><font size=2 face="sans-serif">Hi Utkarsh,</font>
<br>
<br><font size=2 face="sans-serif">Thanks for this nice description of
this new architecture!</font>
<br>
<br><font size=2 face="sans-serif">Some questions that come to mind : </font>
<br><font size=2 face="sans-serif"> * Your description assumes that
everybody shares the same DOM. How will you deal with plugins? You'll have
to make sure that all clients have the same plugins (at least for those
that involve server-side classes) before connecting to a remote server
where someone else has already started a session, or he will not be able
to load the current state properly...</font>
<br><font size=2 face="sans-serif"> * Some questions about synchronisation
: </font>
<br><font size=2 face="sans-serif"> -You seem to move to an async
client/server design, right? </font>
<br><font size=2 face="sans-serif"> -Are the PushState / Invoke calls
meant to be atomic, that is you will ensure that you do not need to make
2 or more of those calls to move from one valid state to another (think
of the current possibility to link two properties)? The issue is what happens
if messages from different clients gets interleaved...</font>
<br>
<br><font size=2 face="sans-serif">Best,</font>
<br><font size=2 face="sans-serif">Stephane<br>
<br>
</font>
<table>
<tr valign=top>
<td rowspan=2><font size=2 face="sans-serif"> </font><img src=cid:_1_071945C0071941D80031146EC1257761><font size=2 face="sans-serif">
</font>
<td><font size=1 face="sans-serif"> </font>
<tr valign=top>
<td><font size=1 color=#ff8100 face="Arial"><b>Stephane PLOIX</b></font><font size=1 color=#ff8100 face="Arial"><b><br>
Pilote Opérationnel - Visualisation scientifique</b></font><font size=1 color=#0062e1 face="Arial"><br>
EDF - R&D<br>
SINETICS<br>
1, Av du Général de Gaulle<br>
92140 Clamart</font><font size=1 color=#0062e1 face="sans-serif"><br>
</font>
<br><font size=1 color=#0062e1 face="Arial"><b>stephane.ploix@edf.fr</b></font>
<br><font size=1 color=#0062e1 face="Arial">Tél. : +33 (0) 1 47 65 51
10</font>
<tr>
<td valign=top><font size=2 face="sans-serif"> </font><img src=cid:_1_07195500071951180031146EC1257761><font size=2 face="sans-serif">
</font>
<td><font size=1 color=#0062e1 face="Arial">Un geste simple pour l'environnement,
n'imprimez ce message que si vous en avez l'utilité.</font></table>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>utkarsh.ayachit@kitware.com</b>
</font>
<br><font size=1 face="sans-serif">Envoyé par : paraview-developers-bounces@paraview.org</font>
<p><font size=1 face="sans-serif">13/07/2010 22:49</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">A</font></div>
<td><font size=1 face="sans-serif">paraview-developers@paraview.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Objet</font></div>
<td><font size=1 face="sans-serif">[Paraview-developers] Plans for changes
to ServerManger (Paraview 4.0 or later)</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Folks,<br>
<br>
As some of you may be aware, we are working on bringing collaboration<br>
support to ParaView enabling multiple ParaView clients to collaborate<br>
with each other. To make it easier to keep ServerManager's among<br>
clients synchronized as well as to reduce the client-server<br>
communication in general, we are currently investigating restructuring<br>
the internals for ServerManager -- mainly how proxies create VTK<br>
objects an communicate with them. This wiki summarizes the proposed<br>
design.<br>
<br>
http://paraview.org/ParaView3/index.php/ServerManager_2.0<br>
<br>
This generally won't affect developers writing custom applications or<br>
plugins. However, we are planning on changing the<br>
views/representations to move more logic to VTK-level as a part of<br>
simplifying the client-side logic. So, expect some changes to how<br>
views and representations are currently managed in ParaView. (This<br>
document does not talk about those changes. We are currently playing<br>
with some prototypes and once we have some better idea, we'll have<br>
some things posted.)<br>
<br>
These changes are still in early development stage. So changes in<br>
ParaView proper are still a quarter or two away.<br>
<br>
As always, any feedback is highly appreciated.<br>
<br>
Utkarsh<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
Paraview-developers@paraview.org<br>
http://public.kitware.com/mailman/listinfo/paraview-developers<br>
</font></tt>
<br><pre>
Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.
Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.
Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________
This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.
If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.
E-mail communication cannot be guaranteed to be timely secure, error or virus-free.
</pre>