mjustin

Maybe this helps: "How can I keep a Free Pascal console application running "forever"?" https://stackoverflow.com/questions/14090697/how-can-i-keep-a-free-pascal-console-application-running-forever (it is related to the Indy TIdHTTPServer also) Basically a ReadLn could be a solution to keep the server running. But this does not answer the "or until I stop ..." part of your question and is worth a separate question. I suggest to ask the question as a new post in the Delphi-Third-Party / Indy subforum at https://en.delphipraxis.net/forum/35-indy/.

This page says for SMTP it is still accessible without modern authentication, and explains why (existing hardware which can't be updated): (Yes, the text on this page may be hard to read, as it is related three types of authentication - Basic authentication, SMTP AUTH. and modern authentication). But regarding Basic authentication and SMTP AUTH, it gets clearer by reading the the linked article "Improving Security - Together" at https://techcommunity.microsoft.com/t5/exchange-team-blog/improving-security-together/ba-p/805892 But if SMTP AUTH is not permitted (and therefore not enabled) by the organization, there are little choices. Microsoft recommends using the Graph API:

Can you be more specific, what is the exact problem? SMTP can still be used with basic auth. Modern Authentication is not required. (However, it is a security option, which can be enforced and configured by the organization)

It will not receive any feature updates, see this note on https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online Original announcement is here: https://techcommunity.microsoft.com/t5/exchange-team-blog/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/ba-p/608055

According to https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-8361e398-8af4-4e97-b147-6c6c4ac95353 sending e-mails via SMTP from Office 365 / Microsoft 365 should work with these settings: Server: smtp.office365.com Port: 587 Encryption: STARTTLS User name / Password: as given in https://account.microsoft.com/

In https://stackoverflow.com/questions/71993040/delphi-11-1s-firedac-and-mysql-ssl-connection-error-unknown-error-number there is one fresh comment saying "I solved the same problem today, downgrading the MySql version to 8.0.23", and one answer "I installed and uninstalled MySQL (and MySQL Workbench and MySQL Script) probably 10 times. The last install worked. I have no idea why this was necessary.". Maybe this or one of the other answers / suggestions may be helpful.

Which exact versions of the 32 OpenSSL DLLs have you tried? Are they 1.1.x or 1.0.x versions?

Next week I will go through the Sectigo CSC request again, it worked well last year. Not sure which browser - IE or Edge - I used last time. The reseller gives step-by-step instructions for Edge configuration are detailed and include many screenshots. They also offer the option to send a CSR, instead of using a browser. Maybe this is an option for those where the IE / Edge is not working as expected. I don't have experiences with K-Software, as I use a different reseller (PSW).

android.content.ServiceConnection is an interface (see https://developer.android.com/reference/android/content/ServiceConnection) Your code must (aquire or) create an instance of a class which implements this interface. If you create it in your code, you must at least implement the two non-default methods, as shown in your Java example.. type TMyServiceConnection = class (TInterfacedObject, JServiceConnection) public procedure onServiceConnected(JComponentName name, JIBinder service); procedure onServiceDisconnected(JComponentName name); ...

If this is related to EN 16931 (https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/EN+16931+compliance), maybe this code is helpful: https://github.com/LandrixSoftware/XRechnung-for-Delphi (open source, dual-licensed)

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.