STOMP Client Libraries for Delphi and Free Pascal

Typical use cases of message brokers include: load balancing (distributed processing), client notification in multi-tiered applications, dynamically configuring and controlling software, alerting and logging, and integration with ISAPI, PHP, .NET, Python or Jakarta EE based web applications.

Yes, basic technical support via email is included until the subscription expires. Advanced and experimental features such as (for example) SSL/TLS, third party libraries, Linux, non-Unicode Delphi versions and message broker configuration are not covered by the basic technical support plan.

On the library home page you will find a link to the download area for registered users. The credentials (user name and password) will be sent to you after puchase.

A trial version with precompiled units (DCU) is not available. To see if the library works, you may use the free demo applications which are included in the demo download file. Also, you may contact Habarisoft to receive additional source or binary code examples.

Yes, the full library source code is included in the installer.

By purchasing a license, you agree to our Terms of Service.

Yes, each developer that uses our products must have their own license.

No, the licenses are perpetual. However, you will be using the last product version released before your subscription expired.

Yes, all minor and major updates are included until the subscription expires.

A download link will be sent within 48 hours. If you do not receive the mail in your inbox, please check your spam or junk folder. If you still cannot locate it, please contact us.

Yes, p lease contact us, and we’ll send you a Paddle manual invoice with the necessary details. Manual invoices allow payment by wire transfer or by other means, such as a credit card.

Please visit the customer portal page.

You will have a one-time opportunity to update the names, tax ID, and address on your invoice on the customer portal page.

Please visit the customer portal page.

No, the source code is not redistributable, even if you change it. Compiled library units are also not redistributable.

Only a network library is required. Please check the feature matrix for available options.

Indy is hosted on GitHub at https://github.com/IndySockets/Indy.

No, just add the Indy directories Lib\Core, Lib\Protocols and Lib\System to the project search path. The Indy version which is included in Delphi may remain unchanged.

Yes, all library versions support transactional sending of messages. Transactional message ack currently is provided for ActiveMQ and RabbitMQ.

Yes, when it is used correctly and as designed, no memory leaks will appear.

Yes, service applications can use the library to communicate with the message broker, if connections are not used concurrently by different threads.

Yes, ISAPI DLL modules can use the library to communicate with the message broker, if connections are not used concurrently by different threads.

No, using a connection concurrently by different threads is unsafe. If different threads need to communicate with the message broker, every thread must use its own IConnection object.

This is not recommended. STOMP is layered on top of TCP, which is a byte stream, not message-oriented. When you use a single TCP connection for both sending client frames and receiving server frames, problems arise. For a detailed explanation, please read the FAQ section in the Getting Started document (version 9.5 or newer).

No, the library only supports the STOMP wire format.

The library includes two experimental adapter classes for usage with OpenSSL, one for Indy (Internet Direct) and one for Synapse. Technical support for these adapter classes and OpenSSL configuration is not included in the basic support package.