Version 10.2 of the Habari STOMP Client libraries for Delphi and Free Pascal is now available for ActiveMQ, Artemis, OpenMQ and RabbitMQ. It turns two compile-time options into run-time settings and fixes two defects that could stall or corrupt a connection. New Line-length limit at run time. Cast the connection to IMaxLineLength and set MaxLineLength before calling Start. This helps when … Continue reading Habari STOMP Client libraries 10.2 released
PREVIEW: What’s New in Habari STOMP Client 10.2
Version 10.2 of the Habari STOMP Client libraries moves two settings that used to require a recompile into ordinary properties on the connection, and fixes two defects that could stall or corrupt a connection at run time. As always, the same code works against all four supported brokers. New New: The maximum length of a STOMP … Continue reading PREVIEW: What’s New in Habari STOMP Client 10.2
PREVIEW: The timeout that wasn’t
Every read in the mORMot2 transport took a timeout parameter, and none of them honoured it. Here is why a Receive(1000) could wait forever, and what changed. Affects: mORMot2 comm adapter only Unaffected: Indy, Synapse Products: all Habari Client libraries (for ActiveMQ · Artemis · OpenMQ · RabbitMQ) Verified on: Delphi 2009, FPC 3.2.2 The symptom Select … Continue reading PREVIEW: The timeout that wasn’t
PREVIEW: Failover, configured from code
Connecting across a list of brokers no longer means recompiling the library. The failover: transport is now switched on at runtime, per connection, through a small interface on IConnection. Why the define had to go Habari has long understood a failover connection URL — failover:(stomp://a,stomp://b) — that tries each broker in turn and reconnects with backoff when a connection can … Continue reading PREVIEW: Failover, configured from code
PREVIEW: Setting the line‑length limit from code
A new MaxLineLength property on IConnection replaces the HABARI_X_MAXLINELENGTH compile‑time switch — so one application can raise the limit for one connection without rebuilding the library. Applies to The Indy transport. Synapse and mORMot2 accept the value and ignore it. New API IMaxLineLength in BTCommInterfaces, implemented by every IConnection. Supersedes HABARI_X_MAXLINELENGTH — still honoured, now with a deprecation warning. The problem Indy caps how long … Continue reading PREVIEW: Setting the line‑length limit from code
STOMP vs. MQTT Explained: Choosing the Right Protocol for Your Messaging Needs
When comparing STOMP and MQTT, the choice often comes down to use case. MQTT excels in IoT scenarios where bandwidth and device resources are limited. STOMP, however, offers clear advantages in enterprise messaging: it’s human-readable and easy to debug, supports both queues and topics, integrates seamlessly with established brokers, and provides transaction handling along with extensible headers.
Messaging for Web and Mobile with Apache ActiveMQ Classic
The presentation covered challenges with HTTP messaging, advantages of STOMP and MQTT protocols, and examples of using STOMP over WebSocket for browser messaging and MQTT for mobile apps.