My Kernel Service Model

[amd64pager]

Yes ,I do.

[amd64pager]

Active objects are like this:
Lets imagine two objects,X and A
If they were active objects,they would go like this:

thread 1 thread 2
X calls A A does its work for X
X does its normal work A gets ready to post its data to X
X receives the data A does its normal work
X calls A A does its work for X
X does its normal work A gets ready to post its data to X
X receives the data A does its normal work

If they were passive:

X activity A activity
X calls A A does its work for X
X does its normal work A gets ready to post its data to X
X receives the data A does its normal work
X calls A A does its work for X
X does its normal work A gets ready to post its data to X
X receives the data A does its normal work

In other words,active objects are like always active,while passive objects are idle when other objects are working.


And in my kernel,I plan to implement this like this:
There is a active object manager service.(passive)
A service contacts it to create an active object.(passive)
Then a worker thread is created to run that object.(active)

When an active object contacts another active object by using the active object manager service,the active object manager service creates a new worker thread to run that call.An message is left in the message buffer when it completes.

[amd64pager]

Thanks for the helpful reply.

Has anyone got more ideas for the model?