Did anyone use ListChanged from a remote WCF portal?

cardasim posted on Tuesday, July 10, 2007

Hi, everybody,

This is my first post on this forum and I take the chance to express my consideration on
what you are doing here. I really respect that.

The scenario:
Client - Server application, the data portal is hosted in the server as a WCF service (WcfPortal) and is accessible though a netTcpBinding endpoint.
I want to maintain a list of entities in the server application and to be able to notify
all server clients when a change in the list occured for some reason (for example some new items arrived from an external system).
1. The list must be created on the server and then be available to the clients
2. Any change occurs in the list on the server side, the ListChanged event should be
transfered to clients

My problem finds somehow an answer at http://forums.lhotka.net/forums/thread/5527.aspx "PropertyChanged not raised with remote data portal". In this post, Rocky says that this feature is not
directly supported by the CSLA framework, but that it is possible to implement such remote event notification (by using a MarshalByRef observer etc - details at the specified link).

However, I was not able to do it until now. I'm just asking myself if is there any chance that I could implement this feature together with my CSLA business objects, or I should drop the idea and simply use the standard CallbackContract from WCF?

Did anyone use a similar scenario until now?

Thank you!

P.S. Just in case I did not manage to describe clearly enough my scenario, please find a similar one,
already implemented with WCF, at  http://dotnetaddict.dotnetdevelopersjournal.com/wcf_alarmclock.htm. Instead of the Alarm event I would like to use the ListChanged in my scenario.