Currently, when a unknown but matching resource is seen, an entirely new Resource object, along with the applicable ResourceHandler objects, is created for that path. This is excessive, and could cause excessive memory consumption if many dynamic resources are created.
This shouldn't be an issue for the intended purpose of this tool - for CoAP testing and small-scale projects - but would still be nice to address.
Currently, when a unknown but matching resource is seen, an entirely new Resource object, along with the applicable ResourceHandler objects, is created for that path. This is excessive, and could cause excessive memory consumption if many dynamic resources are created.
This shouldn't be an issue for the intended purpose of this tool - for CoAP testing and small-scale projects - but would still be nice to address.