![[aMess - a Messaging Program]](/media/logo.gif)
|
aMess
a Messaging Program
|
|
Architecture
At this point, the big pictue have been seen, but the bulding blocks have
neither been depicted nor linked one to the other. This chapter thries to do
it all at once.
Services glue logic
As each service covers one type/class of work each interface (using aRDF and
aQL) implements the desired functionality. For the same reasons that aMess
they will be implemented in Perl, and can be accessed as a Perl module (from
Perl code) or from a SOAP interface. The former let's access it with a
minimum performance penalty, but the latter allows it to be accessed from
any operating platform (any combination of operating system, programming
language, etc.) More work is needed, because the hash type is not defined
in other languages than Perl, so I guess that is passed as an array !!
To avoid this penalty (SOAP to call the class services plus SOAP to call the
ultimate implementation) we call it as Perl modules, giving that the core is
built using Perl.
![[aMess documentation]](/man/media/logo.gif)
|
aMess
a Messaging program
|