crawled from : Msdn
Monday 11 March 2013
A Message Flow in ASP.NET Web API OData - .NET Web Development and Tools Blog - Site Home - MSDN Blogs
What exactly happens from the moment this message arrives at the server until the new Customer gets added in the backend? Let us take a closer look. Stop 1: Parse the incoming URL into OData Path Segments The very first stop is a custom Route Constraint that parses the incoming request URL into a list of OData Path Segments.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment