[Tinyos-devel] Queues with remove(element), isEnqueued(element),
and other commands
dmm at rincon.com
Fri Jun 22 22:11:17 PDT 2007
I agree that Queue interfaces could be more useful by stepping back and
looking at all the different use cases to combine them into one set of
useful interfaces. Since Queueing and other infrastructure building blocks
are essential for quick development of TinyOS applications, it would be wise
to make a unified queue interface as useful and robust as possible.
After talking with Phil some more about this, what we'll do is pull the new
FifoQueue component out of the baseline for now so its interface is not
permanently cast into TinyOS. Then, we'll define some broad, useful Queue
interface to support many the types of behavior, including the ones you are
mentioning. Finally, we (anybody) can implement various Queues using the
unified Queue interfaces.
From: tinyos-devel-bounces at Millennium.Berkeley.EDU
[mailto:tinyos-devel-bounces at Millennium.Berkeley.EDU] On Behalf Of Hugo
Sent: Friday, June 22, 2007 4:45 PM
To: tinyos-devel at Millennium.Berkeley.EDU
Subject: [Tinyos-devel] Queues with remove(element), isEnqueued(element),and
Hello tinyos devel team
I would like to know what to do think of this suggestion. I've been
using modified queue-type components in some applications, I find them
very useful, as they provide both queue and simple list
For example, with RoundRobinResourceQueueC, since it uses only one bit
per client (like a check box), the command remove(element) would allow
a checklist funcionality.
I think QueueC and the new FifoQueueC would also gain with
remove(element) and isEnqueued(element) commands, useful for priority
removal from queue (for example, that's what I use it for). FifoQueueC
already has the reset() command, very useful, but the others don't.
What do you think?
Tinyos-devel mailing list
Tinyos-devel at Millennium.Berkeley.EDU
More information about the Tinyos-devel