On 11/11/2010 9:10 AM, am am wrote:
This is a good idea. But I was thinking that this way the records will be kept
for a long time. Until the application restarts. If there is no standard
mechanism to detect client failure (and also distinction between client failure
and network failure), I will use your idea
You could have your clients put out a request "I am here how about you"
periodically and if the server does not get one of these for 2 or 3
cycles , it cleans up.
You could have the server initiate the request, if the client has a
mechanism to receive such a request and respond.
________________________________
From: Ron Wheeler<[email protected]>
To: [email protected]
Sent: Thu, November 11, 2010 2:47:03 PM
Subject: Re: Using CXF asynchronously
On client startup can you not send a message to the server?
If the server has outstanding records, it deletes them.
If not, it ignores the message and return an "I am ready" message.
On 11/11/2010 1:59 AM, am am wrote:
Hi,
I have a web service that needs to keep some kind of session with the web
clients.
I.e. a client sends request to the web service, the service makes some
internal
records and can associate the client's requests with the records. Additionally
the web service makes call backs to the client according to internal events,
and
sends notifications to the client according to the internal records.I.e.
server
acts also as a client.
My problem is, if the client restarts, then these records become stale. This
means that the client and the server are inconsistent and the client will
receive notifications based on the stale records.
Is there a standard approach to solve this? I was thinking of sending some
kind
of specific request to the client by the server, in the callbacks, and if I
get
an HTTP 500 I clear the records, but I do not know if this is a good idea.
Can anyone make a suggestion on this please?
Thanks!
