[Paraview-developers] RE Plans for changes to ServerManger (Paraview 4.0 or later)

[Stephane PLOIX]

Hi Utkarsh,

Thanks for this nice description of this new architecture!

Some questions that come to mind : 
 * 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...
 * Some questions about synchronisation : 
  -You seem to move to an async client/server design, right? 
  -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...

Best,
Stephane


  
 
Stephane PLOIX
Pilote Opérationnel - Visualisation scientifique
EDF - R&D
SINETICS
1, Av du Général de Gaulle
92140 Clamart
 
stephane.ploix at edf.fr
Tél. : +33 (0) 1 47 65 51 10
  
Un geste simple pour l'environnement, n'imprimez ce message que si vous en 
avez l'utilité.




utkarsh.ayachit at kitware.com 
Envoyé par : paraview-developers-bounces at paraview.org
13/07/2010 22:49

A
paraview-developers at paraview.org
cc

Objet
[Paraview-developers] Plans for changes to ServerManger (Paraview 4.0 or 
later)






Folks,

As some of you may be aware, we are working on bringing collaboration
support to ParaView enabling multiple ParaView clients to collaborate
with each other. To make it easier to keep ServerManager's among
clients synchronized as well as to reduce the client-server
communication in general, we are currently investigating restructuring
the internals for ServerManager -- mainly how proxies create VTK
objects an communicate with them. This wiki summarizes the proposed
design.

http://paraview.org/ParaView3/index.php/ServerManager_2.0

This generally won't affect developers writing custom applications or
plugins. However, we are planning on changing the
views/representations to move more logic to VTK-level as a part of
simplifying the client-side logic. So, expect some changes to how
views and representations are currently managed in ParaView. (This
document does not talk about those changes. We are currently playing
with some prototypes and once we have some better idea, we'll have
some things posted.)

These changes are still in early development stage. So changes in
ParaView proper are still a quarter or two away.

As always, any feedback is highly appreciated.

Utkarsh
_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org
http://public.kitware.com/mailman/listinfo/paraview-developers




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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20100715/a7f10387/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1816 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20100715/a7f10387/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1151 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20100715/a7f10387/attachment-0001.gif>