C
Court Jester
Hi all,
Excuse me if this is wrong forum for this but I've implemented a
protocol handler for my socket server using the state pattern and it
works fine until I attempt to introduce heartbeats which are sent
independently of the client process on the same socket to the server.
Now the state can be processing commands and finds that it has received
a message for the client and this contravenes the protocol and state
transition is inconsistent.
So much for trying something new. What have other people used to solve
this?
It has been suggested that I use a seperate port on the same machine to
send heartbeats but, well, I want to know that that command socket is
responsive and alive.
Erm. thats it.
Ta
CJ
Excuse me if this is wrong forum for this but I've implemented a
protocol handler for my socket server using the state pattern and it
works fine until I attempt to introduce heartbeats which are sent
independently of the client process on the same socket to the server.
Now the state can be processing commands and finds that it has received
a message for the client and this contravenes the protocol and state
transition is inconsistent.
So much for trying something new. What have other people used to solve
this?
It has been suggested that I use a seperate port on the same machine to
send heartbeats but, well, I want to know that that command socket is
responsive and alive.
Erm. thats it.
Ta
CJ