The LLP client and server components described in these sections are included for legacy backward compatibility only. They are not supported for new application development. If you are developing a new application, use Iguana as the transport mechanism for sending messages over LLP, and use the Iguana plugin API to define an interface between your application and the Iguana server. For more details on using plugins in Iguana, see Working With Plugins. For reasons why you should use Iguana instead of Chameleon for your LLP solution, see Why Choose Iguana Over Chameleon?.

The approach supported by the LLP components supplied with Chameleon represents a specific TCP/IP socket architecture, which is:

• Asynchronous Event Driven;
• Non-blocking;
• Single threaded; and
• Uses a message loop.

By no means is this the only valid way to architect a TCP/IP server or client application. Another approach might be having a single listening thread that spawns each connection onto its own thread with blocking socket calls. This is not an approach supported by the LLP components supplied with Chameleon. If you have a requirement for such an architecture, it will be necessary to implement the LLP protocol directly using a sockets implementation native to your environment.