> For that reason I wrote if it is possible to make it async
> earlier.
Yes, put your code in the event.
> I know that I can put something like "Sleep(100)"
No, that will stop the thread for 100ms so nothing more happens.
If you really can handle events, you can use something like this:
On 14/03/2016 13:11, Ertan Küçükoğlu wrote:
MagIpLog1.StartLogging;
if Label2.Caption = 'OK' then begin
Label3.Caption := 'Connection OK!';
MagIpLog1.StopLogging;
What async means is that the MagIpLog1.StartLogging returns immediately,
not after the connection has been
> I have prepared two test projects. There is one TMagIpLog
> component dropped on form for each project. One test project is
> listening its local TCP port
Impossible to say what is wrong from your partial code and lack of any
attempt to log activities in the applications. You should be
: [twsocket] Pinging multipe hosts
> // PING OK. DO DIRECT TCP CONNECTION
> if not TestClientConnection(ClientIP, Err) then begin
> Result := '***ERROR: Client TCP connection fail.';
If you really want to do these tests from the server, this needs to become
async.
You create
> // PING OK. DO DIRECT TCP CONNECTION
> if not TestClientConnection(ClientIP, Err) then begin
> Result := '***ERROR: Client TCP connection fail.';
If you really want to do these tests from the server, this needs to
become async.
You create an array of TWSocket or TMagIpLog components,
> Below is my code where I need to complete my pre-tests. I will
> appreciate, If you can advise as to how to
> manage what I am trying to do.
Which does not use any ICS functions or events apart from ping, and is
really beyond the scope of this mailing list which is for TWSocket
support.
But
LicenseType, Result);
Result := StringToTableToXML(Result);
end;
-Original Message-
From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of Angus
Robertson - Magenta Systems Ltd
Sent: Sunday, March 13, 2016 7:35 PM
To: twsocket@lists.elists.org
Subject: Re: [twsocket] Pi
rom: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of Angus
Robertson - Magenta Systems Ltd
Sent: Sunday, March 13, 2016 11:04 AM
To: twsocket@lists.elists.org
Subject: Re: [twsocket] Pinging multipe hosts
> I will be writing both server and client softwares. No need for a web
>
> I will be writing both server and client softwares. No need for a web
server.
Then it is easy for you to add an application level ping. That is each
server will response to a simple command ("Hello") with a simple answer
("OK").
One or more clients can periodically send that "Hello " command
> I will be writing both server and client softwares. No need for a
> web server.
In which case the server should only ever listen for TCP connections
from clients, which open the connection and send a hello packet once a
minute to prove they are alive, expecting a response so they know the
> 2- clients that complete ping without error, do additional test
> if client software is actually running.
What client software, something you wrote or different? Does it
contact the web server or vice versa.
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please
> *Subject:* Re: [twsocket] Pinging multipe hosts
> *From:* Ertan Küçüko_lu <ertan.kucuko...@1nar.com.tr>
> *To:* "'ICS support mailing'" <twsocket@lists.elists.org>
> *Date:* Sat, 12 Mar 2016 19:34:21 +0200
>
> I thought, at first, that ping might be a
' <twsocket@lists.elists.org>
Subject: Re: [twsocket] Pinging multipe hosts
> I have a Windows service application. That needs to check if several
> hosts
(IP numbers,
> no need to DNS resolve) are still alive. Assuming easiest way to ping
them. Since that will
> require no
> I have a Windows service application. That needs to check if several hosts
(IP numbers,
> no need to DNS resolve) are still alive. Assuming easiest way to ping
them. Since that will
> require no installation on my clients at all. Please suggest other ways
that you think apply.
Ping messages
14 matches
Mail list logo
