>>In Silverlight 3 didn’t they introduce a duplex WCF service? Yes they introduced duplex WCF services, *but* it is doing "long" polling under the hood...
Messages from the server to the client within a particular session are sent using an HTTP response to a* long lasting HTTP request* the client makes to the server (the “long poll”). The client side implementation of the polling duplex protocol ensures that the server always has such pending HTTP request available; as soon as the server sends a message to the client using the response to the long poll, the client issues a new long poll. From http://tomasz.janczuk.org/2009/09/scale-out-of-silverlight-http-polling.html .peter.gfader. http://peitor.blogspot.com/ On Thu, Jan 28, 2010 at 4:17 PM, John OBrien <[email protected]>wrote: > Peter, > > We used sockets in Silverlight2 to prototype a spatial collaboration > concept. The main issues we faced were: > > 1. Needed to run a windows application (testing=console app, > production=windows service) for both server side processing and also as a > policy service. Made it hard to deploy. > > 2. Very raw technology, we had to deal with packets of data and > worried about robustness of the server solution under heavy load. > > > > In the end we didn’t move beyond the prototype but decided we need to > evaluate the purchase of a socket based communication server (often used for > online games). > > > > In Silverlight 3 didn’t they introduce a duplex WCF service? > > > > John. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Peter Gfader > *Sent:* Thursday, 28 January 2010 1:33 PM > *To:* [email protected] > *Subject:* "Real" time updates to and from clients > > > > Hi All, > > > > I play around with "real time" updates to and from SL clients, and have > figured out a couple of possibilities with Silverlight. > > 1. Sockets > 2. Polling over WCF in SL2 or SL3 (HTTP) > 3. WCF net.tcp protocol in Silverlight 4 (Polling over TCP Sockets) > > Anyone has some good or bad experience with them? > > > > Regarding > > 1. Performance > 2. Ease of development > 3. Security (Firewalls are not a problem) > > > > My opinion so far: > > 1. Sockets > > > 1. Harder to write than calling a WCF service > 2. Best option regarding performance > > > 1. Polling over WCF (HTTP) > > > 1. Not a nice solution regarding performance > > > 1. WCF net.tcp protocol in Silverlight 4 (Polling over TCP Sockets) > > > 1. Under the hood sockets, but I don't have to worry about sockets > 2. Good performance > > Port restrictions to all of those I have seen... > > > > Your opinions? > > > > PS > > This guy has a nice Socket implementation for getting updates from a > server > > http://petermcg.wordpress.com/2008/06/05/stock-list-demo-part-3/ > > > > This guy is writing about WCF net.tcp in SL 4 > > http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html > > > > > PS2 > > What can I do against port restrictions? > > > > .peter.gfader. > > http://peitor.blogspot.com/ > > > > > > > > > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
