Hi, I disagree ... TinyOS is a tiny Operating System. It has a scheduler and it manage memory (resources). These are characteristics of OS. The modules, configurations are NOT available due to TinyOS but they are available due to NesC. Someone can write code in NesC without using TinyOS.
best regards, Faisal > Hi Adi, > Thank you very much. > Can I ask you something else? Can we say that modules/configurations are > components? > > Thanks > > 2010/1/5 Adi Mallikarjuna Reddy V <[email protected]> > >> TinyOS is not really an operating system and it is not a middleware >> also. TinyOS uses component model at compile time and single static >> image at >> run time. TinyOS allows applications to be constructed from a large >> number of very fine-grained components (modules and configurations). >> >> Mate can be considered as a middleware on top of TinyOS. >> >> Regards >> Adi >> >> >> On Tue, Jan 5, 2010 at 6:23 PM, Alfred NOBEL >> <[email protected]>wrote: >> >>> Hi All, >>> Please, can we consider TinyOS operating system as a middleware? if yes >>> how is that? >>> Thank you so much. >>> >>> -- >>> Best regards, >>> Alfred.Nooobel >>> >>> _______________________________________________ >>> Tinyos-help mailing list >>> [email protected] >>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >> >> > > > -- > Best regards, > Alfred.Nooobel > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
