On 9/11/07, JaeHyun Roh <[EMAIL PROTECTED]> wrote:
>
> So what if we have an IScheduler interface, and simply have multiple
> > schedulers that inherit from this interface.
> > Which scheduler is used could be configurable, and the right scheduler
> > would be started at startup.
>
>
> Yes, I agree. it have to be onfigurable because not only we need to test
> the scheduler's performance but also have to be prepared for the various
> future uses of SharpOS. I think it's good to start from a simple scheduler
> just like FIFO. and then extends on.
>
Yea, I think starting out with a simpler scheduler would be best. But we
have to make sure our IScheduler, and whatever other type instances it
consumes, are generic enough for our needs. If we want to be able to
interchange different schedulers, we have to make sure that we abstract the
commonalities between different scheduler implementations' schemas.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
