A STOMP client library for Embarcadero Delphi and FreePascal, enabling messaging with ActiveMQ and RabbitMQ.
Delphi/FreePascal STOMP Client is a library that implements the STOMP protocol for Delphi and FreePascal applications. It enables these applications to communicate with message brokers like Apache ActiveMQ and RabbitMQ using the standardized STOMP messaging protocol. The library solves the problem of integrating Delphi/FreePascal applications with enterprise messaging systems.
Delphi and FreePascal developers who need to integrate their applications with message brokers like ActiveMQ or RabbitMQ for enterprise messaging scenarios.
Developers choose this library because it provides a reliable, tested STOMP implementation specifically for the Delphi/FreePascal ecosystem with support for multiple network libraries and compatibility with major message brokers.
STOMP client for Embarcadero Delphi and FreePascal.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Specifically tested with Apache ActiveMQ 5.2-5.4.2 and RabbitMQ 3.5.1+, ensuring reliable connectivity to these popular enterprise message brokers as stated in the README.
Offers a choice between INDY for Delphi or Synapse for Delphi/FreePascal, allowing developers to adapt to their project's network requirements and platform constraints, as highlighted in the features.
Works with both Embarcadero Delphi and FreePascal compilers, including iOS fixes, enabling messaging in diverse Pascal-based applications across desktop and mobile platforms.
Implements the STOMP 1.1 protocol specification with raw UTF-8 message support, ensuring interoperability and internationalization capabilities for enterprise messaging.
The library is only tested with older versions of ActiveMQ (up to 5.4.2) and RabbitMQ (3.5.1+), which may not guarantee seamless compatibility with newer broker releases without additional validation efforts.
Using Synapse requires manual download and integration from an external source, adding complexity to setup compared to self-contained libraries, as noted in the README's instructions.
Only supports STOMP 1.1, missing out on features and improvements in STOMP 1.2, which could be a limitation for projects requiring the latest protocol enhancements.
Relies primarily on a blog post for detailed information, which might lack comprehensive, up-to-date examples or formal documentation, potentially slowing down development and troubleshooting.