> What will your threads do? If you are approaching your problem as a spawn > a thread when you > need to do something, you might want to reconsider. TOS Threads are not > intended for that > kind of activity. >
yes, but i really need to handle this kind of job. if you want you can see my programming approach as a sort of a server that accept incoming request and spawn different parallel activities based on the arrived request. i know in the classic tinyos programming we can use tasks, but in that case i need to handle a queue of request for every task and i don't know how to size them a priori. > > Nope. That is it for now. Dynamic Threads are intended for downloading > needed functionality once motes are deployed. very interesting. i was interested also in transfer functionalities from a node to another. i know there is deluge but as far as i know deluge is intended to transfer a whole binary image, not only a piece of code. have i right understood ? with functionality you mean piece of code and not the whole image? > I assume that by a sync function you mean at the synchronous (task) level > of TinyOS. You shouldn't call sync functions from threads. > Rather you must use a Blocking variant that causes the correct context > switch to occur. to create a blocking function i'll take a look in /tos/lib/tosthread/system > eric thanks Mauro _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
