mjustin

Pre-compiled DLLs for Indy are available on https://github.com/IndySockets/OpenSSL-Binaries They are not shipped with Delphi. Make sure you download and install the correct version - there are 32 and 64 bit versions of the DLLs. Which one to choose depends on your application. Installing the Indy source files on the server is not required. "Just put the DLLs in your app's installation folder."

Other way would be for example cURL, or Indy / Synapse / mORMot.

See: https://stackoverflow.com/questions/72636489/tls-1-3-for-net-4-0-under-windows-7#comment128310433_72636489

Regarding support for the latst TLS/SSL, TLS 1.3 is not included in the trunk version of Indy, but there is a pull request which adds TLS 1.3 support (see https://github.com/IndySockets/Indy/pull/299). Other options to enable 1.3 are available by attaching a commercial SSLHandler. Regarding GMail: two-factor authentication input is usually performed using the system browser. Indy's HTTP server is not involved in this step. Maybe you can be more specific what you are missing in Indy? Indy is definitely still supported, and included in all versions of Delphi and working on Windows 10/11. You may download it from GitHub: https://github.com/IndySockets/Indy p.s. regarding TLS/SSL webservers: you may place the (Indy-based) HTTP server behind a reverse proxy such as nginx or Apache HTTPD. The reverse proxy will do all the encryption work, while Indy still only uses HTTP. The reverse proxy must be configured so the clients will communicate with the proxy only. This has many advantages (think of automated certificate renewal for Let's Encrypt).

The SQL for Query2 must contain a WHERE clause to filter out only the rows for the selected employee ID. Also the GROUP BY can not not work because its SELECT clause does not use aggregate functions. GROUP BY id also makes no sense at all, as ID is the record id in the payment table.

Have you compared the requests from SoapUI with the requests sent from your code?

Thanks for clarifying, it is important to know that MQTT refers to the MQseries product from IBM and has nothing to do with “message queue“ 🙂 Some introduction posts which might be useful for others: https://www.hivemq.com/blog/mqtt-essentials-part-1-introducing-mqtt/ and https://www.hivemq.com/blog/mqtt-essentials-part2-publish-subscribe/

Not sure if I understand the scenario, but messages can be configured so users will see them when back online. This is called a durable client (or durable subscription). For reference see https://stackoverflow.com/questions/34150452/receive-offline-messages-mqtt So, somehow the broker is a database, but specialized for asynchronous messaging. (Disclaimer: I dont have any 'expert knowledge' with MQTT, but its features are very similar to those of other open source message brokers I am using)

Messaging over MQTT (or STOMP etc.) has the advantage that there is a dedicated server for communication, which handles message integrity, redelivery, persistence already out-of-the-box. There are many MQTT-capable message brokers available besides Mosquito. It depends on your target infrastructur and client types which is the best choice. For example, these message brokers support MQTT (and many other protocols): * Apache ActiveMQ (classic) - https://activemq.apache.org/components/classic/ * Apache ActiveMQ Artemis - https://activemq.apache.org/components/artemis/documentation/ * RabbitMQ - https://rabbitmq.com/documentation.html They also seem to support MQTT over WebSockets, which means clients may just use the HTTP port to connect.

Habarisoft released new versions of its native STOMP client libraries for Delphi / Object Pascal for integration with popular open source message brokers: Habari Client for ActiveMQ 7.3 - tested with Apache ActiveMQ 5.16.5 and 5.17.2 Habari Client for Artemis 7.3 - tested with Apache ActiveMQ Artemis 2.26.0 and 2.27.0 Habari Client for OpenMQ 7.3 - tested with Eclipse OpenMQ 6.3.0 and 6.4.0-SNAPSHOT Habari Client for RabbitMQ 7.3 - tested with RabbitMQ 3.10.11 and 3.11.3 Release notes can be found at: https://www.habarisoft.com/release_notes.html Home page and demo applications Home page: https://www.habarisoft.com/ About Habari STOMP Client libraries Habari STOMP Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology - which is distributed, loosely coupled, reliable and asynchronous - to build integrated systems, using peer-to-peer and publish-subscribe communication models. The libraries are available for the open source message brokers ActiveMQ, ActiveMQ Artemis, Eclipse OpenMQ and RabbitMQ. ActiveMQ and OpenMQ are also serving as default messaging subsystems in Enterprise Application Servers such as GlassFish, Payara, TomEE+ or WildFly. 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.

A TClientDataSet (together with a TDataSetProvider) can be used. Even when the Connection is closed, the TClientDataSet is still showing all data. This briefcase-model programming style is available since around Delphi 3, where the architecture was branded as MIDAS, later renamed to Datasnap. So basically this is needed: * a TFDQuery * which is connected to a TDatasetProvider, which in turn * is connected to the TClientDataSet. The TFDQuery or its connection may be closed without losing the data in the TClientDataSet Resources: https://docwiki.embarcadero.com/Libraries/Sydney/en/Datasnap.Provider.TDataSetProvider https://docwiki.embarcadero.com/Libraries/Sydney/en/Datasnap.DBClient.TClientDataSet

Did you open port 8077 in the (cloud) firewall? It may be this problem: https://stackoverflow.com/questions/6071396/winhttp-doesnt-work-when-hostname-doesnt-contains-www-error-12029

Habarisoft released new versions of its native STOMP client libraries for Delphi / Object Pascal for open source message brokers: * Habari Client for ActiveMQ 7.2 – tested with Apache ActiveMQ 5.16.5 and 5.17.1 * Habari Client for Artemis 7.2 – tested with Apache ActiveMQ Artemis 2.23.1 * Habari Client for OpenMQ 7.2 – tested with Eclipse OpenMQ 6.3.0 * Habari Client for RabbitMQ 7.2 – tested with RabbitMQ 3.9.22 and 3.10.7 Release notes Full release notes can be found at: https://www.habarisoft.com/release_notes.html Home page, demo download, full documentation: https://www.habarisoft.com/ About Habari STOMP Client libraries Habari STOMP Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology - which is distributed, loosely coupled, reliable and asynchronous - to build integrated systems, using peer-to-peer and publish-subscribe communication models.

The download for the current Indy source code is available on https://github.com/IndySockets/Indy An installation of the components is actually not required, as you can create instances of the various components at runtime. (note: there is a *.lpk file, in Lib\indylaz.lpk, however I have not tried if it works with the current Lazarus version on Ubuntu)

Habarisoft released new versions of its native STOMP client libraries for Delphi / Object Pascal for integration with popular open source message brokers: * Habari Client for ActiveMQ 7.1 – tested with Apache ActiveMQ 5.16.5 and 5.17.1 * Habari Client for Artemis 7.1 – tested with Apache ActiveMQ Artemis 2.22.0 * Habari Client for OpenMQ 7.1 – tested with Eclipse GlassFish 6.2.3 * Habari Client for RabbitMQ 7.1 – tested with RabbitMQ 3.9.18, 3.10.0 and 3.10.2 Release notes Full release notes can be found at: https://www.habarisoft.com/release_notes.html Home page, demo download, full documentation: https://www.habarisoft.com/ About Habari STOMP Client libraries Habari STOMP Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology - which is distributed, loosely coupled, reliable and asynchronous - to build integrated systems, using peer-to-peer and publish-subscribe communication models.

Indy runs on many operating systems including Linux. It should also run on macOS. If you get an "error #5", you may find the cause by debugging, to find the location in your application and the actual operation it tries to perform.

ScroogeXHTML for Object Pascal is a library which supports a subset of the Rich Text Format (RTF) standard. It converts RTF to HTML5 and XHTML standalone documents, or to fragments which can be embedded in other documents. ScroogeXHTML is compatible with Delphi 2009+ and Free Pascal 3.2.0. Version 8.0 is a major release which introduces new options, including customizable post-processing of the (internal) document tree before the final conversion step, and a customizable hyperlink URI builder class. Home page, API, Getting Started PDF, and demo download: https://www.scroogexhtml.com/scroogexhtml_delphi.html Full release notes: https://www.habarisoft.com/scroogexhtml/8.0/docs/api/version.html

To celebrate its 25. foundation anniversary, Habarisoft increased the special discount for ScroogeXHTML Server Deployment licenses: * old discount: 25% * new discount: 50% Order links and editions overview can be found at https://www.scroogexhtml.com/object_pascal.html#order Single Developer License and Server Deployment License terms are explained at https://www.scroogexhtml.com/scroogexhtml_license.html Conditions: the discount is only valid for purchases together with one ore more ScroogeXHTML Single Developer Licenses. License purchases are not refundable. The special discount is only valid for a limited time and can not be combined with other discounts (except volume discounts) and promotions. The discount is valid both for the Java and the Delphi / Pascal version of ScroogeXHTML. Home page, API, Getting Started PDF, and demo download: https://www.scroogexhtml.com/scroogexhtml_delphi.html

Habarisoft released version 2022.02 of its Object Pascal STOMP client libraries for Delphi and Free Pascal integration with popular free open source message brokers. Habari Client for ActiveMQ 7.0 – tested with Apache ActiveMQ 5.15.15 and 5.16.3 Habari Client for Artemis 7.0 – tested with Apache ActiveMQ Artemis 2.20.0 Habari Client for OpenMQ 7.0 – tested with Eclipse GlassFish 6.2.3 Habari Client for RabbitMQ 7.0 – tested with RabbitMQ 3.9.12 Release notes can be found at: https://www.habarisoft.com/release_notes.html Home page, demo download, full documentation: https://www.habarisoft.com/ About Habari Client libraries Habari Stomp Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology – which is distributed, loosely coupled, reliable and asynchronous – to build integrated systems, using peer-to-peer and publish-subscribe communication models.

The error message 'undeclared identifiers' could mean that your Indy version is to old. Try to update to a newer version from https://github.com/IndySockets/Indy Note: you can extract Indy to a separate directory, keeping the original version unchanged. Just configure the project search path to include the Core, Protocols and System directories.

Do you have a test system? If yes, can you reproduce the slowness there? And is it taking a constant amount of time to establish the first connection, ir is it varying? (I remember a similar issue some years ago which only occured in the production server, and was resolved by a new installation of the InterBase server)

ScroogeXHTML for Object Pascal is a library which supports a subset of the Rich Text Format (RTF) standard. It converts RTF to HTML5 and XHTML standalone documents, or to fragments which can be embedded in other documents. ScroogeXHTML converts text attributes including background and highlight colors, paragraph alignment (left, right, centered, justified) and indent (left, right, first line). Unicode conversion allows multi-language documents, including simplified and traditional Chinese, Korean and Japanese. Compatible with Delphi 2009+ and Free Pascal 3.0.4 / 3.2.0. Version 7.3 is mainly a maintenance release which fixed several minor issues. Version 7.2 introduced support for embedded PNG and JPEG images using Data URI. Home page, API, Getting Started PDF, and demo download: https://www.scroogexhtml.com/scroogexhtml_delphi.html Full release notes: https://www.habarisoft.com/scroogexhtml/7.3/docs/api/version.html

Habarisoft released new versions of its Object Pascal STOMP client libraries for integration with popular open source message brokers. some of them known as default messaging providers in WildFly, Eclipse GlassFish and Payara Server. Habari Client for ActiveMQ 6.11 - tested with Apache ActiveMQ 5.16.2 Habari Client for Artemis 6.11 - tested with ActiveMQ Artemis 2.17.0 Habari Client for OpenMQ 6.11 - tested with Eclipse OpenMQ / GlassFish 6.0 Habari Client for RabbitMQ 6.11 - tested with RabbitMQ 3.8.19 and 3.9.0 Release notes can be found at: https://www.habarisoft.com/release_notes.html Home page, demo download, full documentation: https://www.habarisoft.com/ About Habari Client libraries Habari Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology - which is distributed, loosely coupled, reliable and asynchronous - to build integrated systems, using peer-to-peer and publish-subscribe communication models.

Many thanks for your interest! The product pages contain links (labeled 'Buy now') to the order pages, which show the prices including tax. On the home page, the links can be found at the end of the feature matrix. Kind regards

Indy 9.0.50 can be downloaded here: https://github.com/IndySockets/Indy9 Indy 10.6.2 works with Delphi 6 and can be downloaded here: https://github.com/IndySockets/Indy