C

Part 1 of a 2-part series, this is a comprehensive introduction to the AMQP protocol from Danushka Manikkumbura.  This article describes the history and foundational concepts of AMQP, an application layer protocol for interoperable messaging systems.  The second article in the series features a detailed how-to guide for the AMQP transport in Axis2/C.

Axis2/C is commonly used to process and send SOAP messages in a multi-threaded environment. In this article, Damitha Kumarage illustrates the Axis2/C support for thread models, so that users can better understand how libraries will behave in different multi-threaded use case scenarios.

Axis2/C is a SOAP processing engine written in C.  Axis2/C enables C/C++ code to be exposed as Web services, and allows developers to talk to Web services using C/C++ Web service clients.

If you try to look at the internals of Axis2 a little bit beyond the generated stubs, you will see the ServiceClient class. Let us look at what it means.

The Axis2/C architecture consists of flows, phases, modules and handlers.

They can be described as follows. There are two flows called In-flow and Out-flow. A flow is the path from the transport to the service or client.

In this article by Dushshantha Chandradasa, an introduction to the use of the Secure Socket Layer (SSL) protocol for securing online transactions is provided.

In this tutorial, Supun Kamburugamuva illustrates debugging Apache Axis2/C services and clients in both Windows and Linux platforms under different deployment scenarios.

One of the main deployment scenarios of Apache Axis2/C is with Apache Web Server. Best performance and stability can be gained by deploying Axis2/C in Apache. When deployed in Apache server, Axis2/C uses the memory pools supplied by Apache and guarantees zero memory leaks. Also due to custom memory implementation Axis2/C can perform up to its maximum.