Although I have no specific knowledge about this, since the ZR300 shares commonalities with the R200's design, such as identical IR components, it is possible that ROS found that a LR200 launch file worked just as well with the ZR300 (the LR200 is almost identical to the R200 aside from improved RGB and IR emitter components).
The LR200 launch file is discussed more in the link below.
Hopefully someone on this forum will be able to help you with your server question.
Thank you Marty! I was of the same opinion as you at first. But I found that the resolution was configured as half of ZR300 can do, so I wonder if Euclid team did that deliberately for some reasons.
I compared the resolution tables in the data sheet documents of the ZR300 and Euclid and they were identical. However, the data sheet does not always match up precisely to what is actually available to access in the product via its SDK software.
If performance is capped in the software's configuration then usually it is done because the development team believes that there would be a worse user experience in terms of performance lag on that particular hardware device if it were left uncapped.
I just wanted to provide a quick update. I found that someone on the Librealsense forums who was also asking about the launch files said that they could use the R200 launcher to launch the ZR300 using the following instruction:
roslaunch realsense_camera r200_nodelet_rgbd.launch camera_type:=ZR300