<HTML>
<HEAD>
<TITLE>Re: [Paraview-developers] Casual Weekend Read: ProcessModule 2.0</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>My notes:<BR>
<BR>
</SPAN></FONT><UL><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Why does vtkProcessModule have to init functions that must be call sequentially? Why not just have one initialization function?
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Can the client call AcceptConnectionsOnPort? Is that for reverse connections? The documentation that this class is to establish a service.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>The connections methods talk about sockets & TCP/IP. What about other connection types like SSL, HTTPS, MPI, or Portals. They come up.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>How does vtkConnection establish itself with a socket connection managed by the vtkProcessModule?
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>I find logging a bit overrated. I find I would usually rather have synchronous client/server communication where if the server is stopped the client blocks on the last call that initiated the server.<BR>
</SPAN></FONT></UL><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
-Ken<BR>
<BR>
<BR>
On 7/16/10 3:49 PM, "Utkarsh Ayachit" <<a href="utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Folks,<BR>
<BR>
In line with the ServerManager 2.0 documentation, here's another wiki<BR>
summarizing proposed changes to vtkProcessModule. Besides simplifying<BR>
and cleaning up, these changes will make it easier to do the<BR>
following:<BR>
<BR>
* Create/Manage additional socket connections between processes with<BR>
custom protocols<BR>
* Bi-direction messaging i.e. send messages from server-to-client (of<BR>
course protocol will have be defined as such and client will have to<BR>
monitor activity periodically).<BR>
<BR>
Here's a link to the Wiki page:<BR>
<a href="http://paraview.org/ParaView3/index.php/ProcessModule_2.0">http://paraview.org/ParaView3/index.php/ProcessModule_2.0</a><BR>
<BR>
[ Sorry Yumin, no diagram still :). ]<BR>
<BR>
As with ServerManager 2.0 proposal, none of these changes are expected<BR>
to affect ParaView master for a quarter or two. We'll keep everyone<BR>
posted. Again, this is early design, so feel free to voice your<BR>
concerns and suggestions and we can try to address them in the<BR>
implementation.<BR>
<BR>
Utkarsh<BR>
_______________________________________________<BR>
Paraview-developers mailing list<BR>
<a href="Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><BR>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers">http://public.kitware.com/mailman/listinfo/paraview-developers</a><BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>