DNS operational responders can be pool-allocated as they are fixed in size

[andy31415]

Problem

MinMDNS responders are distinct object types, so generally allocated on the heap.

#16181 adds support to manage active responders but using heap only.

Given that we have fixed responder types (SRV/PTR/AAAA/A/...) we could reserve size for each in separate pools and have a guaranteed 'we have space for them' for devices where this is important. The only remaining somewhat dynamic part is TXT content which we can figure out separately.

Proposed Solution

Add the option for pooling responders and allow a limit and pre-allocation size to be set for them. I imagine something like separate pools of each responder size and have some Alloc(...) method for each when needed.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This stale issue has been automatically closed. Thank you for your contributions.