[Paraview] ParaViewWeb

[Sebastien Jourdain]

Hi Ben,

there is several ways to integrate ParaViewWeb into iPython and the
documentation highlight a distributed/in-situ one. (Which is by far the
less obvious one ;-)
In fact, if you are not expecting ParaViewWeb to use directly the in-memory
objects of your iPython MPI engines, you might just deploy a ParaViewWeb on
the side which will naturally allow you to also have it embedded inside
your iPython integration.

For that you will need an apache on the front to do the relay in https/wss.
This should solve the security error.

Regarding the overhead of the server side rendering, we did not wrote any
specific analysis or documentation.
Do you still have render calls when you switch to WebGL on the client side?
Do you have them when you interact with the scene? If so, you can adjust
the JS of the WebVisualizer and disable the camera synchronization of the
WebGL renderer, which will prevent the client to send camera update to the
server. But if you do so, if your data change, your view will revert back
to the original server side camera position.

Hope that helped you in some ways,

Seb


On Sat, Feb 8, 2014 at 4:10 PM, Ben Bales <bbbales2 at gmail.com> wrote:

> Hello,
>
> I have two questions concerning ParaViewWeb.
>
> 1. I want to embed the ParaViewWeb visualizer in iPython. This page (
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ipython) suggests
> the standard way of doing that is embedding an iframe that references a
> ParaViewWeb Visualizer instance.
>
> My iPython instances are handled over an https connection, so embedding an
> http iframe from a separate server will throw security errors in my browser.
>
> Is there any easy solution to get around this? I'd like to keep
> authentication on my servers, but I'd also really like to use the embedded
> Visualizer (cause it's super super cool :D)
>
> 2. Is there any documentation on the overhead of the server-side rendering
> for ParaViewWeb? I noticed by default Paraview still spawns an X renderer
> for every rendering that is happening on the client.
>
> Ideally I'd just like Paraview to not try to render stuff server-side, and
> the client just handle the drawing with WebGL, but I probably am missing
> some critical point about the paraview architecture.
>
> Thanks,
> Ben
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140210/c7a89d66/attachment-0001.html>