[openbeos] Re: SK: interacting modules
- From: "Nathan Whitehorn" <nathan.whitehorn@xxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 15 May 2002 18:55:45 EDT (-0400)
> Hi,
>
> I'm going to work on the Storage Kit modules that are supposed to
> interact
> with components outside the Storage Kit itself. Therefore I'd like to
> start a little discussion with the respective teams. Though I chose
> this
> list initially, I guess, the discussion should be taken to more
> appropriate lists as soon as it is clear (at least clear to me --
> others
> might already know :-) who should actually be involved.
>
> Well, here are the items:
>
> * BMimeType:
> This class provides access to the mime data base. AFAIK it achieves
> this
> by communicating with the registrar, which is actually managing the
> data
> base.
Actually, I think it reads the files manually. It's easy enough to do.
> * Node Monitoring:
> Basically the two functions watch_node() and stop_watching(), but
> who
> does the actual work? Is there a Node Monitor (the BeBook mentions
> something like this)? ...?
These go straight to the kernel.
> * BQuery:
> Static queries can be mapped to the fs_*_query() functions in
> libroot
> and thus are certainly related more closely to the kernel.
> But how is the additional functionality for live queries provided?
> Who
> does this? Are live queries somehow related to node monitoring?
I think all of this happens in the kernel as well.
-Nathan
--
Fortune Cookie Says:
"Imagine if every Thursday your shoes exploded if you tied them the
usual way. This happens to us all the time with computers, and nobody
thinks of complaining."
-- Jeff Raskin, interviewed in Doctor Dobb's Journal
Other related posts:
