SilverlightShow: The duplex story: looking at duplex communication in Silverlight 4 - Part 3: Using Net.Tcp Comments

RE: The duplex story: looking at duplex communication in Silverlight 4 - Part 3: Using Net.Tcp

( alphapapalima) — Mon, 02 Aug 2010 18:43:45 +0300

Yes, right now I do have a wcf service that is basically getting the data from sql server and pushing it to the Silverlight client using net.tcp (every 5 seconds). I read that Query Notifications and Broker should not be used due to performance issues, so I am kind of stuck. I would be interested (when you have time) to see what kind of solution you would come up with.

RE: The duplex story: looking at duplex communication in Silverlight 4 - Part 3: Using Net.Tcp

( Gill Cleeren) — Mon, 02 Aug 2010 09:49:52 +0300

Interesting scenario.

In any case, you'll still need some service sitting in between, because the database itself won't be able to push updates directly, only a service can. I'll perhaps write a sample on my blog if I find some time :)

RE: The duplex story: looking at duplex communication in Silverlight 4 - Part 3: Using Net.Tcp

( alphapapalima) — Fri, 30 Jul 2010 01:37:54 +0300

Great.. I got it working with the net.tcp. Exactly what I am looking for. I am curious though, you had mentioned in the part II, "In scenarios where the client needs to be updated because of changes in the state of the server side (for example a change in a database, a file change…), the best solution is working duplex."

I have that scenario now where a third party application is updating our database. When the database is updated, I would like for it to update our client (silverlight) of the changes. Do you have an example of a database pushing changes to the silverlight client?

Thanks.