Add queue_size arguments to control size of pub/sub queues #2
Description
In offline processing environments (such as building slam maps from recorded bags) it's important to make sure every message is handled correctly.
The input queues sizes are hard-coded to 20 messages and the output queue sizes are hard-coded to 2 messages.
This creates a bottleneck when dealing with bag messages directly.
It would be really useful to be able to pass parametrs to control the size of publish and subscriber queue sizes.
Perhaps pub_queue_size and sub_queue_size?
I don't think it's necessary to specify sizes for the individual topics (cloud, scan).