Hi guys,
Could you please inform,
What is the best way to use in order to be able to keep alive both server and
client?
I would like to keep them both alive.
Is it custom? or systemon? or off?
How about interval?
Thanks
-daniel
--
To unsubscribe or change your settings for TWSocket mailing
What is the best way to use in order to be able to keep alive both
server and client?
Only the client matters, ignore the server. Just design your protocol so
the client sends regular packets, at least one every five minutes, I sent
them each minute, with the server returning an
Thanks Angus,
I think five minutes will be just good for me :)
What is the best way to use in order to be able to keep alive both
server and client?
Only the client matters, ignore the server. Just design your protocol so
the client sends regular packets, at least one every five minutes, I
If the SslWSocket sends command such as: “Time”,
SslWSocketServer is processing it and responding by giving the time to the
client
(this what I have noticed in the samples).
Right.
Now,
Can the same thing be done in the other way around?
SslWSocketServer sends command such as : ”Time”,
Thank you :)
Sounds excellent.
Best regards
-Original Message-
From: Francois PIETTE
Sent: Wednesday, January 19, 2011 7:33 PM
To: ICS support mailing
Subject: Re: [twsocket] SslWSocket processing data
If the SslWSocket sends command such as: “Time”,
SslWSocketServer is processing
Hi guys,
Is there any built in procedure for getting the remote computer’s name?
if not,
I will get the computer name from the client site and send it to the server as
command when the connection is made.
thanks.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
