Ace applications

The following is an attempt at describing the relationship between the different applications in the Acedb package. It is an amateur's view, so if you have comments, or spot errors, please contact me.

 


ACENET GIF


Some comments:
  1. The Ace kernel is not quite as well separated out as it may appear: this is probably changing with the Acelib C API that is now under development.
  2. MacAce has not been updated for a long time and should be considered unsupported at this time.
  3. Gifaceserver combines the functionality of aceserver and giface in one program.
  4. The CORBA server and client are just started projects. [It is also the part I understand the least about so my depiction of these may be seriously flawed.]
  5. Jade2ace used to be called netclient, and simply translates the rpc communications that come out of gifaceserver into sockets stuff, as needed by java.
  6. Jade is a packet of java classes for Acedb. Here you could well place your own java classes.
  7. The xaceclient keeps it's own database on disk, comprising a subset of the full database (that's why the database looks smaller ;-).
  8. Aceclient is a tace lookalike that talks with the gifaceserver.
  9. Webace consists of more modules and scripts than shown. Also, Aceclient.pm is only the frontend to a dynamically loadable module to handle the connection to gifaceserver.
  10. JaceLib is the first real application of the Acelib C API.

Last edited 1997-09-17/staffan