On Jun 6, 2008, at 3:35 AM, Nicola Wegner wrote: > 2008/6/6 Paul Stickney <[EMAIL PROTECTED]>: > [...] >> >> I don't have in-depth enough knowledge about the Collection >> implementations, but I suspect that >> (in priority of where I'd start looking) >> 1) No route is being found and it's waiting and waiting and ... > > This really seems to be the problem. I have put some debug messages in > CtpForwardingEngineP.nc to check it. It retries to send every 10 > seconds. If no route is found it blocks forever. There is an empty > implementation of <event void UnicastNameFreeRouting.noRoute();> that > is signaled. I think this is the place where a cancel after several > retries could be implemented. But this does not really make very much > sense in case of the collection protocol.
The application can always cancel; why should CTP define a policy for you, and have to allocate state (a timer) and code (a timer handler) in order to do so? Phil _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
