I have a problem to solve that I am sure many others have solved before me. I would like to hear how you have solved it, and what the pros and cons are versus other alternatives.
The problem is this: An entity in a client-server application is to be modified by the server, but the client needs to take action in response to the changes. Ideally I would like the entity object to offer events that can be subscribed to whether on the
server or on the client.
We are using remoting, so particulars may apply, although in general the problem of course comes from the client-server nature of the system.
I am unsure if making use of two-way remoting is the way to go. I am not (at least not yet!) talking about pushing changes from one client to another. Rather, a client provides an entity object, the server updates it, and the SAME client responds to changes
in its state. It seems to me I would need some kind of "deferred" event firing mechanism, and I suppose I could implement this in my entity objects. Perhaps put event information in a queue when normally one would raise the event, so they can be raised later
If anyone has any ideas or in paritcular *experience* with solutions to this problem, I'd be very interested to hear your POVs.
View Complete Post