apps

Load balancing/distributed processing, client notification in multi-tiered applications, dynamically configuring and controlling software, alerting and logging, integration with ISAPI, PHP, .NET, Python or Java™ based web applications

check

Yes! Basic support is included for one year. 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 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 when a new release is available.

A trial version with precompiled units (DCU) is not available. To check if the library meets your requirements, you can purchase a Single Developer license, which includes a 14 days full money back guarantee. This allows to test the full version of the library without any risk. The reseller (ShareIt) will give a full refund if you find that the library does not work as expected.

check

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

check

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

block

No, the source code is not redistributable, even if you change it.

Internet Direct (Indy) or the Synapse TCP/IP network library is required.

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

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.

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.

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.

check

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

check

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

check

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

check

Yes! All library versions include support for transactional sending of messages. Transactional message ack currently is provided for ActiveMQ and RabbitMQ.

check

Yes, the core library works with Free Pascal 3.0.2+

No, the library only supports the STOMP wire format.