A 3-tier odata solution for NAR/RESO, with server-side oauth


We followed up the blog post at http://blogs.msdn.com/b/paolos/archive/2013/04/09/how-to-use-windows-azure-table-storage-in-windows-azure-mobile-services.aspx

image

which shows how to create a 3 element system, composed of a windows store client (armed with the ability to use the login  capabilities of the azure mobile packages), a azure mobile middleware site (with which the app collaborates to perform what is technically server-side login), and an odata webapi instance (hosted in a azure store table service).

image

 

image

Though this client gives us one viewer, it is very tuned to login and end user interaction. We can also run the more basic odata–centric viewer client allowing us to directly talk odata/webapi repository of entities underlying the above. We see:

image

We see, from a fiddler trace, the interaction between this odatda client and the odata server (for a JSON-encoded response):

image

alternative, we can remove the accept header and allow the default output format to take emerge:

image

End.

Advertisements

About home_pw@msn.com

Computer Programmer who often does network administration with focus on security servers. Very strong in Microsoft Azure cloud!
This entry was posted in coding theory. Bookmark the permalink.