depending on how many clients there are each one can call a method on the server that never returns (Thread.sleep). if the method ever returns in the client it knows the server has died. this obviously only works for a small number of clients.
My server notifies my client when it finished a job through the
observer method. However, it is possible that the server dies (or the
network connection gets broken), and I need to detect this. I
implemented a thread which continously "pings" (calls a simple
remote_obj.ping) and rescues any exceptions in this method call. Is
there a better solution out there?
--
we can deny everything, except that we have the possibility of being better. simply reflect on that.
h.h. the 14th dalai lama
My server notifies my client when it finished a job through the
observer method. However, it is possible that the server dies (or the
network connection gets broken), and I need to detect this. I
implemented a thread which continously "pings" (calls a simple
remote_obj.ping) and rescues any exceptions in this method call. Is
there a better solution out there?
depending on how many clients there are each one can call a method on the server that never returns (Thread.sleep). if the method ever returns in the client it knows the server has died. this obviously only works for a small number of clients.
a @ http://drawohara.com/
--
we can deny everything, except that we have the possibility of being better. simply reflect on that.
h.h. the 14th dalai lama
hmm that's good idea for keeping connections alive i guess i had problems that frequent requests over ssl were making huge overhead.
i had problems that frequent requests over ssl were making huge overhead.