Silverlight Line of Business Application, Transport Layer

At least I’m trying.  And that’s how I’ll get better, too.

In Silverlight 2 the coordination between a web application and the Silverlight client application application ( one that doesn’t use Astoria  Data Services  ) needs to be built by the application programmer.

In a few of my Silverlight projects, I’ve used the method I’ll describe below and it’s working fine.  I have to say though that my user-base and simultaneous user count isn’t large so I haven’t tested this method under high volume situations.

Here is an architectural view of how the software packages and sends data from Silverlight client to Web Server.

The package of source code which is presented with this article is a LOB application I’m writing for EZBurn Manufacturing – EZBurn’s app will at some point consist of tools to manage customer communications, production drawings, production line processes, and overall health of operations.  These pieces were pulled out of this demo package, but I’ve left all the code which is responsible for communicating back and forth to the web server and business logic containers.  There’s a Google Maps sample for you if you drill down to a person record, it’s kind of interesting.  Another piece I left in is the Silverlight History component.  That ensures your ability to use Deep Linking.

I discussed the serialization and compression sources in a previous blog post:  http://faxt.com/blog/post/2008/08/SOA---Server-to-Silverlight-and-Back.aspx

Please feel free to email me with questions – I have to apologize for being so short on this post, but MAN – there aren’t enough hours in the day for my spring yard cleaning and today is a bright, sunny day just made for gardening.

Here’s the source

Here’s the running application so you can see it in action