make outputQueue configurable

As the number of incoming connections the outputQueue shall be configureable to allow for specific use cases:

Broker needs high number of input sockets and output queue size for small messages.
Eventings only require a limited number of sockets and thus also a smaller queue size to not exhaust the associated memory pool.

pt::tcp::PeerTransportSender::PeerTransportSender(xdaq::Application* owner): Task("tcp/PeerTransportSender"), xdaq::Object(owner), outputQueue_(4000,0.8), channelMutex_(toolbox::BSem::FULL,true)

Originally submitted on sourceforge by Roland Moser ( rmoser ) - 2009-02-16 15:13, #2605698

Edited Dec 05, 2018 by Luciano Orsini

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information