Dan Wahlin http://www.TheWahinGroup.com (@danwahlin)
He makes use of the Silverlight Enabled – WCF service). Simpler. Class decorations are no longer required. Deprecated.
Simpler version of fiddler. Trick to get fiddler to recognize localhost is to append a period (http://localhost.). Will throw an issue if you don’t have a client access policy file.
WCF binary inspector – a plugin for fiddler adds a WCF tab, allows you to decode your binary encoded message.
Another option for faster performance is to use TCP ports (faster, but limited ports).
WCF Duplex Service – Have server push data to your client app.
- Supported by HTTP Duplex Polling with multiple messages per poll
- Silverlight 4 supports WCF TCP calls
- sample by Yavor Georgiev at http://blogs.msdn.com/silverlightws
- http://tinyurl.com/nettcp – good tutorial
Demo of sending video 10 fps via WCF and using TCP bindings. Not as fasy using HTTP bindings.
Discussed with him after session to confirm that nothing has improved with WCF 4.0 and SL 4 in terms of solving the issue of duplicating classes if you share classes across services. IE, we are doing the correct approach when we share class libraries between WCF and SL apps. He couldn’t believe that Proliance was still using WSE, FWIW.
No comments:
Post a Comment