Hi,
I've got the same problem like many others: I need my Web Service to "push"
the data to its clients, ideally generate an event to which the clients
listen. Yes, I know that they are not built for this, and that http is
stateless, and there is .Net Remoting, and many other things as well. I just
hope may be someone has a work-around or may be something new has been
introduced since the last post and whitepapers were published on the subject.
Web service suits my project architecture 99%, except the need to pull the
data. Among other things, it is designed to be the "middleman" between the
clients and the database that resides on the same server as the Web Service.
I need the clients to know immediately about any change in the database. The
problem is that my application is time sensitive and polling every 15 sec
(like the IssueVision application) is not acceptable. The problem is also in
the number of concurrent users. My application is about to be distributed to
the organizations that vary significantly in the number of users. On top of
that, I'm far from being an expert in .Net technologies and thus can't make a
strait and confident choice between different technologies and tools.
Your help will be very much appreciated.
Anna
