Angus Robertson

Thanks, you are outside my experience with databases of those sizes, it might be worth trying backup from SSMS once to see if it's doing something magical to get better speeds, but I suspect it's just running those same commands. My backups used to be slower, until I went for SSDs everywhere with 32G of memory, but not highly loaded. Angus

Sounds like you are doing it correctly already! FORMAT means write a new file, otherwise it will add backups to an existing file. But I've not used these commands. How long is your backup taking for what size file? Angus

Backup and restore can be scripted, ie USE SQLTestDB; GO BACKUP DATABASE SQLTestDB TO DISK = 'c:\tmp\SQLTestDB.bak' WITH FORMAT, MEDIANAME = 'SQLServerBackups', NAME = 'Full Backup of SQLTestDB'; GO but admit I've never tried to automate it in over 10 years, not sure if ADO supports the GO command. All my Delphi applications interact with SQL using stored procedures to separate the two languages and all easier SQL testing. Angus

Everything in SQL Server depends on the database size, and disk speed. I distribute a database to multiple web servers weekly, using SSMS backup (about 30 secs), then restore on the web servers, about 15 seconds, for a 700MB DB, a 3GB DB takes a few seconds longer, I know these are not really that large.... Then a minute to update the credentials. Angus

Again, look at numerous samples and components that verify certificates in different ways, OpenSSL actually does it for you, provided a root bundle is loaded, which is automatic with recent ICS versions. You should be using the TSslHttpRest which means this is all automatic, see the OverbyteIcsHttpRestTst sample. Angus

All the HTTPS samples show the certificate for the connection, try one of them and see what you get? PeerCerrt will be blank unless you also set SslVerifyPeer true in the context. No idea what "C.FD.TLS-S" means, TX509 has lots of properties for the numerous parts of the certificate, none of which are base64, you'll have to search. Angus

PeerCert is a parameter passed in the onSslHandshakeDone event, as illustrated in dozens of samples and components, such as OverbyteIcsHttpsTst1.pas. Angus

Thanks, a registry patch fixed it, added to my long list of other patches and tools used to make Windows behave as I'm used to. I normally use Ultra Explorer, an old Delphi app from Mustangpeak that was open sourced, and built with D2007, keep meaning to update to modern compilers, but it uses dozens of components that need removing or replacing. Angus

My major annoyance with Windows 11 is they keep changing File Explorer, rarely for the better. Specifically there is a new right click menu with the default options, but you have to click again on Show More Options to see the historic menu we've had for 25 years with addon like TortoiseGit, TortoiseSVN, 7Zip, etc. Somehow WinRAR seems to be on both menus, so maybe there is a new API other developers have not found yet to get onto the first right click menu. Angus

A new TOAuthOption type of OAopAuthNoCliSecret should fix it. Angus

If you can privately email the 'public' ClientId for next week, that will save a lot of time setting up Azure, which is always a nightmare. Angus

So effectively supporting a public ClientId requires the ClientSecret to be specified before GetToken, GrantAuthToken, etc? Have you tried changing ClientSecret immediately before these methods? I'm not doing any development for a few days, busy with something else. Angus

Sorry, no quick answer, a public client seems the opposite of the OAuth2 concepts. My Azure credentials are currently expired or dead, so no recent testing, but I'll look into this next week. Angus

The web server component has several events for the processing of requests, the exception will be in one of those events. Angus

Under what circumstance does the exception happen? In which component. WSocket is used in all components. Most ICS applications that receive data have code in the onDataAvailable event handler to handle that data, and an unhandled exception during that code can result in your error, so it is unlikely to be an ICS problem. I'd ensure all exceptions in the event handler are handled and logged, rather than letting them fall into the ICS error handler. Angus

I've updated the ICS MQTT client and server components to support protocol 3.1.1, previously we only supported 3.1. Not finished testing, not checked all packets yet. The client will connect to a v5 server by ignoring dozens of new options, but needs a lot more work, much more complicated than v3.1.1. Also added a lot more logging so we see the packets being sent and received, and added more options to the sample. In SVN now, the overnight zip will be updated this evening. Angus

I always return REST Json responses with a results wrapper, success/fail, to avoid the client needing to parse for data. But your change is made, and will be in SVN this week. Angus

The REST component does a simple check for {}, but would miss Json that comprises only array elements without any objects, which I assumed was very rare. But adding such a check is trival, meanwhile you can just parse ResponseRaw, albeit with the risk of failed parsing from non-Json text. Angus

No, OpenSSL is widely used with threaded programs, provided those programs are written correctly. Angus

Windows itself uses a thread for each async socket. Angus

On the general issue of using threads, remember that the ICS web and FTP servers support hundreds of simultaneous clients without using threads, I've never understood why so many people assume that threads are necessary to do two or more client connections at once. Unless they are migrating from using blocking components... when the code should be rewritten properly. At some point, there will be a new ICS threaded server component, since threads are necessary to use more than one CPU, but the server will generally only need one thread per CPU, with multiple clients in each thread. Angus

Using threads to handle multiple components in parallel is unnecessary, provided you are using async methods, so fully event driven. I've done tests with hundreds of components running in parallel, the SSL negotiation takes a while so eventually limits the number in parallel. The FTP component should usually be created and destroyed within the thread. There is a specific component for your purpose, TIcsFtpMultiThread in OverbyteIcsFtpMult.pas with a sample OverbyteIcsXferTst. Angus

I've added a new event OnWSFramesDone to the Websocket client, called when the queue of frames has been sent, for flow control when sending a lot of data. Previously, the OnWSFreameSent was called after each frame, but it was not easy to tell if this was the last queued frame. I've only tested it with a few frames of ASCII, the HttpRest sample really needs a new button to send a queue of files, which is on my list, but also needs a server able to accept those files. But I'm sure you'll tell me if it does not work. In SVN now, will be zipped overnight. Angus

I've just installed Bonus KSVC 7.0 OK. Angus

ICS V9.4 is ready for RAD Studio 12 Update 3, aka RAD Studio 12.3, and specifically the new 64-bit IDE. The ICS Delphi V9.4 design packages already have Windows 64-bit as a target, allowing them to be installed into the 64-bit IDE. The 32-bit IDE allows design packages to be built with target Windows 64-bit, but not installed. Note the 64-bit IDE does not support Windows 32-bit targets, only Windows 64-bit. If you use the IcsInstallVclFmx.groupproj Build Group, all design packages will be built for Windows 64-bit. All the main samples build OK in the 64-bit IDE, with a Windows 64-bit target being automatically added, unfortunately even when deliberately missing such as the OverbyteIcsNetMon sample that does work in Windows 64-bit. Currently, GetIt only works in read-only mode in the 64-bit IDE, so you will need to install ICS using GetIt from the 32-bit IDE, then start the 64-bit IDE and manually install the three design packages. The ICS V9.4 C++ Builder packages can be currently be installed successfully into C++ Builder 12.3 32-bit IDE for the Windows 32-bit target only. The 32-bit IDE should be able to build for Windows 64-bit and Win64x (Modern) as well, all the package paths are correct, but both targets currently give compiler errors. The C++ Windows 64-bit errors are four unresolved external, and the same error happens in Delphi 11, so should be fixable by someone with C++ knowledge. Building for Win64x (Modern) gives lots of undefined symbol errors due to RAD Studio being unable to import other packages compiled built with C++ Win64x, this error was reported six months ago for C++ 12.2 but is not fixed in 12.3. So ICS can not be used in the C++ 64-bit IDE that only supports Win64x (Modern), not Windows 64-bit. Separately, there is a new version of the DD Service Application Framework used by two of the ICS samples, adding support for 64-bit IDE Wizards. Available shortly from https://www.magsys.co.uk/delphi/ddservice.asp Angus