I am looking into building a web-based viewer for Electronmicroscopy data with server side rendering and have been experimenting with the capacity of both vtk.js and ParaViewWeb to do so.
From what I understand, vtk.js uses a function called ImageStream to be compatible with remote-side rendering, creating a second overlay in the browser, which the user then moves, and ImageStream sends that mouse movement to the server, which moves the server-rendered cone. There is an example of this functionality here.
ParaViewWeb has a class RemoteRenderer which reads mouse movements in the browser, renders frames, and then sends the rendered frames to browser when they are ready to be viewed.
So first, is my understanding of what each of these softwares is doing accurate?
Additionally, ParaViewWeb has it’s own function called WSLinkImageStream, but I haven’t found documentation on what WSLinkImageStream does or how it is similar/different/compatible with vtk.js’s ImageStream.
Ultimately our team would like to be able to use both ParaViewWeb’s capacity for server-side rendering, and vtk.js’s capacity for minimal representation overlays in browser in an EM viewer. How can we go about integrating these softwares?