a. The TinyOS Resource interface does not allow a component that already has a request in the queque for a resource to make a second request. Suggest a reason.
b. However, the TinyOS Resource interface allows a component holding the resource lock to re-request the lock. This request is enqueued for a later grant. Suggest a reason for this policy. Hint: What might cause there to be latency between one component releasing a lock and the next requester being granted it?
We need at least 10 more requests to produce the solution.
0 / 10 have requested this problem solution
The more requests, the faster the answer.