Theoretically yes. But in practice having multiple clients connected
to the same server is an open problem because the server was written
with the assumption that it has only one client controlling it. There
is slightly more support in the code for having the client connected
to multiple other processes (pvservers or possibly something else) but
it is not a well traveled path either.

Utkarsh has done the most work in these direction. He has gotten as
far as having a proof of concept prototype working for a Phase I SBIR.
But finishing the work is the subject of a Phase II SBIR that he is
about to start in on.

In summary, ParaView can't do it now without modifications. The
modifications are non trivial. And we are working on it.

David E DeMarle
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x109



On Mon, Oct 26, 2009 at 5:42 AM, Olumide <[email protected]> wrote:
> Hi -
>
> I'm aware that Paraview operates/implements a client-server paradigm. This
> suggests that it may be possible for an external (e.g. C++ application) to
> communicate with a running instance of Paraview, by sending it commands
> (e.g. open legacy VTK file) via the port attached to the server.
>
> I'd appreciate pointers on how to do this.
>
> Thanks,
>
> - Olumide
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Reply via email to