split openni_launch for resource-constrained systems [closed]
What is the best way to split openni_launch into some modules running on a (resource-constrained) robot with an Asus Xtion Pro Live sensor providing raw data, and processing modules running on a (powerful) remote PC, performing registration and point cloud construction?