Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

12 Good

1 Follower

About mitzi

  • Birthday 07/17/1970

Technical Information

  • Delphi-Version
    Delphi 10.3 Rio

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. New version 14.1.0 released * TMiTeC_MUS - Fixed available updates detection in 32-bit version + TMiTeC_MUS - Added Update History detection and available updates detection information extended + TMiTeC_MUS - Added Demo 32 * TMiTeC_Storage - Fixed assigning logical drives to physical devices + TSysProcMonThread - Added additional settings properties (PerformanceMeasuring, EvaluateSecurityInfo, RetrieveProcessIcon, RetrieveProcessVersionInfo) For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page
  2. New version 14.1.0 released + Trusted Platform Module detection added (TMiTeC_Machine.TPM) * Windows Product Key decoding rewritten and fixed + Added Windows available updates detection (MicrosoftUpdateSession)(MSI_MUS.pas, TMiTeC_MUS)  For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page
  3. New version 14.0.0 released + TProcListMonThread, TSysMonThread, TProcMonThread and TSysModListMonThread merged to new one - TSysProcMonThread (MSI_ProcListMon.pas, MSI_SysMon.pas, MSI.ProcMon.pas, MSI_SysModListMon -> MSI_SysProcMon.pas) + TMiTeC_SysProcMon - CPU usage measuring rewritten and precised - process cpu cycle time is used to usage calculation + TMiTeC_SysProcMon - CPU clock frequency evaluation rewritten - now it is based on real power distribution + TMiTeC_SysProcMon - Handle enumeration rewritten to reflect latest available APIs + TMiTeC_SysProcMon - System process module enumeration added + TMiTeC_SysProcMon - Windows 2000 compatibility fixed + TMiTeC_SysProcMon - Thread start address symbol evaluation + TMiTeC_Security - added product state, component rewritten->new interface + TMiTeC_SMBIOS - Windows 2000 compatibility fixed + TMiTeC_Storage - added SMART data reading for USB disks + TMiTeC_SMBIOS - initial SMBIOS 3.4 compliance + TMiTeC_SMBIOS - Hardware Security table 24 added + TMiTeC_SMBIOS - OEMM strings table 11 added + FPC/Lazarus compatibility  For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page
  4. mitzi

    TSimpleWebSrv and POST

    It's a pitty. It could be perfect for webhook implementation.
  5. ICS v8.63 Hi, Is TSimpleWebSrv able to process POST request with some data (JSON) in body? GET works as expected but POST returns (to Postman) 404 and OnSimpWebSrvReq event is not triggered. Thanks
  6. Of course I did. But when i set TimeoutConnect either to 5 or 5000 OnTimeout event was triggered after 3-4 seconds after Connect was called regardless of TimeoutConnect value. So I'm a little confused.
  7. Thanks, that's it. And timeout is defined in seconds or milliseconds?
  8. hm, i'm trying, but despite the fact I have BUILTIN_TIMEOUT defined, property TimeoutConnect has no effect 😞 What is scale? Seconds or milliseconds?
  9. Well but this is what I ask for. How did you (or others) solve this scenario? Your suggestion is ping. Well, when ping is successful it tells me nothing about my TCP server, if it is running and listening or not. Other suggestion is to abort connection attempt with timer. But it creates new problem with socket reusing. So what? It seems there's no useful advice. I will try to make my own port scan via WinSock.Select with timeout set to 5 secs (as I did in my post above for Delphi Socket component) before TWSocket.Connect. Disadvantage is when server is on, then i will do two connection attempts. First by port scan and second with real client connect. Another one is that this is blocking attempt. 😞 Anyone has better solution?
  10. If client connect attempt to primary server fails, it needs immediately to connect to another one. If socket is in use even after timer 'breaks' connection attempt by Abort, then next immediate attempt will fail too due to socket is in use, won't it?
  11. Your suggestions are no usable. ICMP is security issue and it is no allowed in our environment. Also it only checks IP address accessibility. Not TCP server itself. Other suggestions does not allow the socket to be immediately reused for new connection attempt. Do you really think my request is so stupid?
  12. No I don't have this intent. I found ICS very usable, but this is, in my opinion, key property ICS should have. I just wanted to point that this timeout is possible to be set. You wrote it is not possible by design. It seems it is not true. So my question is whether it is possible to implement this timeout setting to ICS? Consider this situation. I have primary TCP server and backup TCP server. Clients are connected to primary one. If this primary server goes down for any reason, then client loses connection and tries to reconnect. But it can take 20 secs now than it finds server is really inaccessible and then connects to backup server. This reconnection should be as short as possible. Mostly if client is not able to connect within 5 secs server can be considered as inaccessible and then connection to another backup server is processed. But 20 secs is really too long. Your recommendations how to solve this problem when connection timeout cannot be set?
  13. If ICS uses WinSock.Select for connection then timeout can be set via latest parameter. Look at following code sample. I modified method from Delphi System.Win.ScktComp.pas and it does exactly what I want. Sets timeout for connection attempt to 5 secs. Originally it took 20 secs too. But I can't use these components :(. procedure TCustomWinSocket.DoOpen; var v: integer; WrSet : TFDSet; TimeVal : TTimeVal; begin DoSetASyncStyles; Event(Self, seConnecting); v:=1; IOCtlSocket(FSocket,FIONBIO,v); try CheckSocketResult(Winapi.WinSock.connect(FSocket, FAddr, SizeOf(FAddr)),'connect'); TimeVal.tv_sec:=5; TimeVal.tv_usec:=0; FD_ZERO(WrSet); FD_SET(FSocket,WrSet); if Select(0,nil,@WrSet,nil,@TimeVal)<>1 then CheckSocketResult(1,'select'); finally v:=0; IOCtlSocket(FSocket,FIONBIO,v); end; FLookupState := lsIdle; if not (asConnect in FAsyncStyles) then begin FConnected := FSocket <> INVALID_SOCKET; Event(Self, seConnect); end; end; Couldn't be something like this implemented to ICS?
  14. Another question: Is there some timeout for connection attempt? When TWSocket tries to connect to server and server does not exist (non-existing ip address or non-listening server) it takes 20 secs than OnSessionClosed is triggered. Can this timeout be changed/set? Thanks for your support
  15. Is it possible to use TSslWSocketThrdClient descendant instead of TSslWSocket on client side? I tried and it worked except one thing. OnSessionClosed is triggered only once and then never again.