12-19-2012, 12:46 PM
You're right, I added client-side options.
But it works, so that the server receives UDP packets from the client, and if the server is turned off and back on, it does not know how to set the output until get the package from the client. Server does not know what is the address of the client(because there may be many) and can not send the package to the client.
There are two ways to solve the problem.
1.Easier to implement: Add option, the server will remember the outputs stats before off and after turning on them set. Only that this option has one drawback: as the server is turned off and at that time will change the status of the client INPD it will not be noticed.
2. Difficult to implement: Server will remember client IP(the last client package before off) and when you turn on, serwer sends requesting packet to the client the transfer of the current state of INPD.
The first solution is sufficient or not?
But it works, so that the server receives UDP packets from the client, and if the server is turned off and back on, it does not know how to set the output until get the package from the client. Server does not know what is the address of the client(because there may be many) and can not send the package to the client.
There are two ways to solve the problem.
1.Easier to implement: Add option, the server will remember the outputs stats before off and after turning on them set. Only that this option has one drawback: as the server is turned off and at that time will change the status of the client INPD it will not be noticed.
2. Difficult to implement: Server will remember client IP(the last client package before off) and when you turn on, serwer sends requesting packet to the client the transfer of the current state of INPD.
The first solution is sufficient or not?
pozdrawiam
tomek
tomek