The end user has no means of controlling the
DATAGRAM_SOCKET_BUFFER_SIZE, which is set to 64 *
If you have many sessions open (20 of these buffers
are kept per session) and a long queue of informs
this quickly becomes a lot of MB in RAM. In many
applications 64 * 1024 is unneccessary large. My
application works fine with only 2 * 1024.
The buffers DEFAULT_RECEIVE_BUFFER_SIZE and
DEFAULT_SEND_BUFFER_SIZE are currently possible to
change with constructors. Something similiar for the
DATAGRAM_SOCKET_BUFFER_SIZE would be very useful.
The issue is loosely related to request 1562072.