The MAFFinder was designed to be complaint to the MASIF standard. The main differences
in this version to the standard are the following:
The name of methods of the
MAFFinderIFace are changed to be
conform to the Java code writing style from SUN[
SUN]. This means that
all method names containing more then one word (e.g.
lookupAgent) are
written with the first word lower case but internal words capitalized. This
means for example for the MASIF MAFFinder method
lookup_agent that
it is called
lookupAgent in Java. The parameter of all methods are
the same, using Java classes for CORBA definitions.
The MASIF standard uses CORBA for all communication. The design of the MAFFinder
in the TAgents System is basically independent of the communication form.
The protocol dependent parts are separated into the MAFFinderServiceProxies,
like there are implemented the RMIMAFFinderServiceProxy and
the PLSMAFFinderServiceProxy. To make the MAFFinder here compatible
to the standard one would have to write a CORBA communication service and providing
it with a CORBAMAFFinderServiceProxy. This proxy would have
to implement the MAFFinderIFace with the corrected names to
fit exactly to the standard and would have to make the real MAFFinder in this
way accessible for other (not TAgents) Systems over CORBA. This task
should be able to do very similarly as the RMICommService
and it should be possible to re - use many parts of the RMI protocol implementation.
