Authentication in WP7 client with REST Services–Part II

In the previous post I covered the “semi-passive” way for authentication between a Windows Phone 7 client and a REST service. This post completes the information with the “active” way. There’s nothing unexpected here really: We call the Identity Provider using a RequestSecurityToken message (RST) We send the SAML token to ACS and get a…

0

Windows Azure Architecture Guide – Part 2 – TailSpin Surveys – AuthN and AuthZ

Tailspin Surveys is a multitenant, SaaS solution, targeting many different customers. Some of these customers might be “enterprise” with “Big-IT” and are likely to demand advanced integration capabilities for identity (e.g. identity federation). Others, potentially smaller, are likely to not require these. Even smaller companies (e.g. someone working from home) might even want to reuse…

0

Windows Azure Guidance – Failure recovery – Part III (Small tweak, great benefits)

In the previous post, my question was about a small change in the code that would yield a big improvement. The answer is:   What changed? No try / catch We reversed the order of writes: first we write the details, then we write the “header” or “master” record for the expense. If the last…

4

Windows Azure Guidance – Additional notes on failure recovery on Windows Azure

Things will eventually fail in your application and you need to be prepared. So most components should be designed for something going wrong and recover gracefully (or as gracefully as possible) and leaving the system in a consistent state (eventually in some cases). In this post I wrote about dealing with data consistency when interacting…

1

Windows Azure Guidance – New Code & Doc drop on CodePlex

We are almost content complete for our first Windows Azure Architecture Guide (the most probable name for our book). Available for download today: New updated samples, including all file processing and background tasks (lot’s of small nuggets in there, such as use of multiple tasks in a single Worker, continuation tokens, data model optimization, etc)….

4

Windows Azure Guidance – Background Processing III (creating files for another system)

Last week Scott walked me through his current design for the “Integration Service” in our sample. Here’s some preview of this early thinking. As a reminder, our fictitious scenario has a process that runs every once in a while and generates flat files for some other system to process: it simply scans the database for…

1

Windows Azure Guidance – Background processing II – One worker, two workers, …

Question for you: if your application has 2 “background” task to perform, do you implement this as 2 distinct workers? or as 1 worker with 2 responsibilities? Option 1 is straight forward. Option 2 requires more work, but … does it make sense? It turns out that it does make sense. In some cases it…

3

Windows Azure Guidance – Development Process

One frequent question we get is around “process guidance”. Also known by the more modern and fancy acronym “ALM”: Application Lifecycle Management, which replaced the old SDLC term, which in turn (and only if you are old enough like me) meant something completely different, but I digress…. Application lifecycle management on Windows Azure has some…

1

Windows Azure Guidance – Replacing the data tier with Azure Table Storage

This new release focuses primarily on replacing the data tier with Azure Table Storage. To make things more interesting, we changed the data model in a-Expense so it now requires two different related entities: the expense report “header” (or master) and the details (or line items) associated with it. The implementation of this on SQL…

1