Management software

for aeronautics

Applications developed over the X.400 Client API can be deployed in two ways:Over X.400 P7, to access the X.400 Message Store. This is useful for client applications that require storage services from X.400.Over X.400 P3 to directly access M-Switch X.400. This is useful for client applications that provide their own reliable storage, and wish to transfer messages over X.400 without the overhead of a Message Store.The X.400 Client API is intended for both standalone client applications, and for Web applications, and offers multiple language bindings (C, Java, and Tcl) to enable this.Deployment TargetsThe Isode X.400 Client API is designed for use by vendors building X.400 client applications, in particular AMHS applications (aviation industry), EDI applications and Military applications using STANAG 4406 (P772).Key BenefitsThe Isode X.400 Client API offers the following benefits:For developers of X.400 client applications, it provides a very simple abstraction.Although the X.400 complexity is abstracted, the API is designed so that all X.400 services can be selected and modified if required.The API is cross platform - available on Windows, Linux, and Solaris.The same basic API can be used for deployment over either P3 or P7.ArchitectureThe X.400 Client API can be used in two distinct ways, as illustrated below. In the first architecture, the library connects the application to M-Switch X.400 using P3. This is appropriate for X.400 applications that need to send and receive messages, and deal with message storage as a part of the application.