Silverlight 4 Beta Networking. Part 2 - RSS,ATOM,JSON
Play Silverlight 4 Beta Networking. Part 3 - HTTP POST
Description
A set of short screencasts providing a "tour" of the network capabilites in the Silverlight 4 beta. We'll look at raw HTTP access, socket access and WCF capabilities.
In this video, we take a look at doing a simple HTTP POST with both the WebClient and HttpWebRequest/Response APIs.
The next video in this series is here and the previous videos are;
Part 1 - WebClient and HTTP GET, XML
Part 2 - WebClient and HTTP GET, RSS, ATOM, JSON
Download
Right click to download this episode
- WMV (97.5 MB)
- MP3 (10.3 MB)
- Low Quality MP4 (52.9 MB)
- Mid Quality WMV (75.2 MB)
More episodes in this series
Silverlight 4 Beta Networking. Part 4 - Cross Domain HTTP
Related episodes
Silverlight 4 Beta Networking. Part 12 - WCF and Polling HTTP
Silverlight 4 Beta Networking. Part 11 - WCF and TCP
Silverlight 4 Beta Networking. Part 10 - WCF and HTTP
Silverlight 4 Beta Networking. Part 9 - UDP Multicasting
Silverlight 4 Beta Networking. Part 8 - TCP Sockets
Silverlight 4 Beta Networking. Part 7 - HTTP & Forms Auth
Silverlight 4 Beta Networking. Part 6 - HTTP and Basic Authentication
Silverlight 4 Beta Networking. Part 5 - HTTP Methods/Stacks
Silverlight 4 Beta Networking. Part 4 - Cross Domain HTTP
Silverlight 4 Beta Networking. Part 2 - RSS,ATOM,JSON
The Discussion
-
Mike Greenway Am I thinking right? I can ues the HttpWebRequest/Response APIs to send a querry to the server, run the querry over a large XML file on the server and returns just the xml nodes I wish to display/manupulte on the client. A poor mans data base call? Is there anything really wrong with doing this?
-
mtaulty Yes, you can do that if you like. Or you can use WCF and do a similar thing via SOAP services and get a nicer programming model. Or you can use a framework like WCF Data Services to expose a data model ( Entity Framework/LINQ to SQL/Custom ) from the server side over easy to access RESTful services including a standard for how a URI can represent the query over that data. WCF RIA Services would be another choice at a higher level of abstraction stil..
Lots of choices...