Hello,
What do I need to do to get the client number into the server?
As you can see here,
I get the computer’s name, IP and Port but the client number is missing.
---
procedure
What do I need to do to get the client number into the server?
You don't because the client number changes each time a new connection is
added or closed. You have to lookup the number each time you need it.
Or design your application so it's not needed.
Look at the FTP server component and
Message-
From: Angus Robertson - Magenta Systems Ltd
Sent: Tuesday, January 18, 2011 11:48 AM
To: twsocket@elists.org
Subject: Re: [twsocket] TWSocket and Client number
What do I need to do to get the client number into the server?
You don't because the client number changes each time a new
If I have many clients connected and I have all the clients are
listed in a TLISTBOX or in COMBOBOX and I just want to select
one of them and send the command.
So you build your combobox, wait 10 seconds, one client disconnects, all
the clients numbers reduce by one and your combobox is out
Thanks Angus,
So you build your combobox, wait 10 seconds, one client disconnects, all
the clients numbers reduce by one and your combobox is out of date. When
you try to send a command to one of them it may be the wrong client or
you'll get an exception because there are fewer clients.
I
I can't find the message you have sent with the computername in the
packet fields.
Last Thursday morning.
My packets looked like this:
TxData: CV121RML-0002|NN130120080707-170202|20080707-170204||
RxData: CS010PC08|20080707-160204|0|RML-0002|
where CV was a client ident, CS server
My packets looked like this:
TxData: CV121RML-0002|NN130120080707-170202|20080707-170204||
RxData: CS010PC08|20080707-160204|0|RML-0002|
Thanks Angus,
I understand what you mean but this unfortunately is too much for me :(
I can't make/handle this because I don't even know how to handle
On 18-01-2011 11:25, daniel cc wrote:
So you build your combobox, wait 10 seconds, one client disconnects, all
the clients numbers reduce by one and your combobox is out of date. When
you try to send a command to one of them it may be the wrong client or
you'll get an exception because there
That's why you need a server socket listening at each client computer.
Every time the a client computer starts, connect to the Server computer
and introduce himself. Hey, my name is Earl and I'm listening to your
commands at this Address. I will report to you any errors occurring here.
With
I have been trying to use the IP (PEERADDR) and the port (PEERPORT)
in this,
SslWSocketServer1.Client[0].SendStr(ledSendCommand.Text + #13 +
#10); for trying to send with no success.
The command is gonna be typed into a TLabelEdit component which
is text and sending requires integer and I
On 18-01-2011 13:50, daniel cc wrote:
Clients are not having static IP and the place where clients are gonna
be doesn't allow top open any ports for incoming trafic etc.
Connecting from the server to the server placed in clients isn't going
to work in my case or perhaps I am mistaking?
If
Hi Angus,
I am very much pleased and I thank you very much for trying to help me out.
Sorry, but you really are out of your depth here, you need to understand
simple programming first. We can not write your programme for you.
Yes,
I do have limited knowledge for now but, I am learning all
What is the MyPeerAddr? -- Integer?
You can work that out yourself, look at what type GetPeerAddr returns.
If you mean a database table,
Not necessarily, it can a table in memory, made up of records, which you
use to keep track of all clients from which you update your GUI and keep
track of
Hi Angus,
You probably only want to send
a reboot PC command once...
Yes,
commands (just few) will be sent real seldom (once or twice in a week).
Communication will be made mostly by the client ans server will respond by
doing very small things.
It is actually faster to use FClientNo as
14 matches
Mail list logo
