Leaderboard

I would choose the latter. No need to allocate memory dynamically unless the record instance needs to live after TObj.run3() exits. But, if you have a lot of methods of TObj that are acting on the record then they should instead be methods of TRecord itself. Consider refactoring your code to make it cleaner.

TDataItem class is just four units, no dependencies, 100% Pascal code. It can be used standalone from TeeBI. uses BI.DataItem; var MyData := TDataItem.Create https://github.com/Steema/TeeBI

No, simply two monitors with different resolutions (and different scaling): Just to make this more difficult, monitor 2 (1920x1200 scaled 100%) is the main monitor, so all positions on monitor 1 (3840x2160 scaled 125%) are negative x (-1 to -3839) and some are even negative y. I always put the IDE on the right 2/3 of monitor 1, that's why saving and restoring desktops in Delphi IDE's is broken on my setup since Delphi 11. Also this is the reason that scaling in the Delphi IDE is broken on my system (and my home grown scaling in GExperts is very difficult to do and still has some glitches).

You can create a CGI application as a VCL Program that listens for web requests as if it was running under IIS--makes it very easy to debug (see attached image). Maybe this will help: https://github.com/corneliusdavid/AutoGetIt

Hi I noticed that in THttpCli 404 StatusCode is returned in many different situations like timeout/DNS resolution failure, which makes it difficult to diagnose issues because it is the same as legitimate 404 code from web server. Is it possible to change it to something else?

I was about to ask the same thing. 404 status code is misleading in timeouts. My workaround: try except if SslHttpCli1.RequestDoneErrorStr='Custom Timeout' then MyResponseCode:=-1 else MyResponseCode:=SslHttpCli1.StatusCode; end;