Regier Avery J wrote:
> I haven't taken a good look at the rheise.os classes as I should have by now
> (been busy with the day job), but from what I understand, they implement a
> large set of functionality that is intended for jos.core.* (ie. the process
> management).
The source files are available on the web if you want a quick way of
browsing them:
http://www.progsoc.uts.edu.au/~rheise/projects/rheise.os/rheise.os-0.1.4-pre4/src/jos/
This link points directly into the jos.* package so you can see the
package structure that I have proposed. All classes in jos.* represent
the public API which application developers will program against. In
other words, these classes are platform independent. I have placed the
platform dependent classes in josp.*.
A quick outline of the public API structure is as follows:
jos
+ process
+ user
+ security
+ system
So, a programmer would reference jos.process.JavaProcess, just as today
a programmer would reference java.lang.Thread. I have aimed to make the
package names for the most commonly used classes concise.
> With that in mind I think his using jos.core,
> jos.core.process, or just jos.process would be fine. jos.system.* has a
> different purpose from process management.
Just a point of clarification: my jos.system package does not contain
process management functionality. That goes in jos.process as you
guessed.
In fact none of the packges I have place in jos.* are platform
dependent, so jos.core would not be used for these. Perhaps the josp.*
classes can go in there as you suggested. I'm open for suggestions.
--
Ryan Heise
http://www.progsoc.uts.edu.au/~rheise/
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
