- Study the OMA object model.
- Study the basic architecture of CORBA.
- Question: what is the basic step of CORBA programming?
We will look at this in detail on this Friday. The basic steps are:
- Write the IDL definition of the servant object.
- On the server side, compile the IDL with a IDL compiler, which generate
the "skeleton".
- Write the servant implementation, which implement the interface defined in the IDL.
- Start the servant, and register it to the ORB
- On the client side, compile the IDL with a IDL compiler, which generate
the "stub".
- Write the client program, which treats the stub as the real servant.
- The client get an object reference from a string or a name server.
- Question: what is the size of a typical ORB?
Leave to this Friday.
- Question: does CORBA provide real-time specifications, like QoS, priority, and scheduling?
There are Real-time CORBA and Minimum CORBA SIG's in the CORBA community.
People are getting serious about the real-time embedded applications using CORBA. The status of these communities needs to be checked.
- Question: What are the known-uses of CORBA?
Need to be surveyed. Leave to Friday.
- People need to do their home work. We choose the study group format in order to get more people involved.
People agree that CORBA focuses more on architectural flexibility than on
performance issues. It is not obvious that it is suitable for real-time
embedded systems. We hope to have a better understanding of this issue
after the study groups on CORBA and TAO.
We will continue on this Friday. The focus will be the problems raised today.
comments to: liuj@eecs.berkeley.edu