Deep Fried Bytes: A Lap Around OData with Mike Flasko

Deep Fried Bytes

In this episode, Woody sat down with Mike Flasko at MIX10 to chat about OData that was announced on the second day of the conference. OData is an open protocol for sharing data. It provides a way to break down data silos and increase the shared value of data by creating an ecosystem in which data.

Running time
0h36m
File size
34.00MB

Download Original File | View original post

Episode synopsis

In this episode, Woody sat down with Mike Flasko at MIX10 to chat about OData that was announced on the second day of the conference. OData is an open protocol for sharing data. It provides a way to break down data silos and increase the shared value of data by creating an ecosystem in which data consumers can interoperate with data producers in a way that is far more powerful than currently possible, enabling more applications to make sense of a broader set of data.

Thanks to our guest this episode

Mike Flasko 2007 01

 

Mike is a Senior Program Manager Lead in the Data and Modeling Group at Microsoft. Mike and his team are focused on the Open Data Protocol (OData) and the WCF Data Services Framework (previously known as Project “Astoria”). Prior to working with OData and WCF Data Services, Mike was a PM on the Windows Network Developer Platform team at Microsoft, where he was responsible for the System.NET namespace (.NET Framework), the Winsock API and the Winsock Kernel API. Prior to his roles in Program Management, Mike worked as a .NET Developer Technology Evangelist.

Mike can be contacted via the Data Services Team blog: http://blogs.msdn.com/astoriateam/

Show Notes

Download Show

You might also like...

Comments

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” - Brian Kernighan