Building the Conduit C++ REST Server to send data to mesh viewer

[HuckZou]

Xingrui needs to look into Conduit Relay examples and figure out how to use the API to build a server that sends Blueprint format data from the server to a mesh viewer client.

[xjrc]

@Averrie, @tunedere: After speaking about this with Cyrus and hammering out what the simplest path forward would be for this issue, we decided that it would probably be easiest for you two to complete this task by modifying an existing Conduit Relay server example so that it outputs Blueprint mesh data. This solution will allow you both to create a new Relay server that leverages Relay's existing functionality without having to worry about creating an independent binary. Here's a general overview of the steps you'll need to follow:

• Set the LLNL-Collaboration fork of Conduit as a new remote for your local Conduit repository.
• Update your local Conduit repository to include the latest changes from the LLNL-Collaboration fork (i.e. run git fetch [new-remote-name] followed by git merge [new-remote-name]/master).
• Review the node viewer server class, the node viewer test code, and the websocket example code.
• Create a new C++ class for the Blueprint mesh server using the node viewer server class as a template. This class should be placed in the src/libs/relay directory.
• Modify the src/libs/relay/CMakeLists.txt file to include the new C++ class header and source file paths in the conduit_relay_headers and conduit_relay_sources variables, respectively.
• Add a test that can launch the Blueprint mesh server using the node viewer test code as a template. The source for this test code should be placed in the src/tests/relay directory.
• Modify the src/libs/relay/CMakeLists.txt file to include the new test file path in the RELAY_TESTS variable.
• Execute the new test by navigating to Conduit's build-debug directory, running make -j8, and then running ./tests/relay/[new-test-name].
• Commit all the new code and then push it to the LLNL-Collaboration Conduit repository (i.e. run git push [new-remote-name] master).

I hope that this makes the path forward a bit more clear. If anything in this explanation is confusing, please let me know and I'll do my best to clarify.