RDNodeResource class should not presume "coap" as scheme when setting context ("con"). Instead use Request.getScheme() when constructing context. If this fails, try inferring the scheme from request option "Uri-Port".
RDNodeResource now uses Executors.newSingleThreadScheduledExecutor(new Utils.DaemonThreadFactory(....)) instead of Timer. This improves over the current version where a new Timer object (hence a new thread) is created every time RD life time is set and would only one timer task always.
RDNodeResource class should not presume "coap" as scheme when setting context ("con"). Instead use Request.getScheme() when constructing context. If this fails, try inferring the scheme from request option "Uri-Port". RDNodeResource now uses Executors.newSingleThreadScheduledExecutor(new Utils.DaemonThreadFactory(....)) instead of Timer. This improves over the current version where a new Timer object (hence a new thread) is created every time RD life time is set and would only one timer task always.
Signed-off-by: Vinod Mukkamala vmukkamala@hotmail.com