The Katana component architecture divides an application into four logical layers, as depicted below: host, server, middleware, and application. The component architecture is factored in such a way that implementations of these layers can be easily substituted, in many cases, without requiring recompilation of the application.
An example of components from different layers
- Host: IIS/ASP.NET, OwinHost.exe, Self-Host/Custom-Host(e.g. Windows Service)
- Server: SystemWeb(ASP.NET pipeline), HttpListener (OwinHost/Self-Host/Custom-Host)
- Middleware: Web API, SignalR, Nancy
- Application: Your Application.
Run your jobs on simple or complex recurring schedules
- Call services inside or outside of Azure
- Run jobs on any schedule—now, later, or recurring
- Use Azure Storage queues for long-running or offline jobs
- Management REST API
Get Started using Scheduler MSDN
Windows Azure Mobile Services:
- Accelerate your mobile app development. Incorporate structured storage in the cloud, user authentication(Facebook, Google, Microsoft, Twitter, Active Directory account)/authorization and push notifications to millions (Notification Hubs) in minutes. Add your custom backend logic in C# or Node.js
- Introduction to Azure Mobile Service – Scott Guthrie
Below are some tutorials that walkthrough common authentication/authorization/push scenarios you can do with Windows Azure Mobile Services:
This tutorial demonstrates CORS support in ASP.NET Web API. We’ll start by creating two ASP.NET projects – one called “WebService”, which hosts a Web API controller, and the other called “WebClient”, which calls WebService. Because the two applications are hosted at different domains, an AJAX request from WebClient to WebService is a cross-origin request.
What is “Same Origin”?
Two URLs have the same origin if they have identical schemes, hosts, and ports. (RFC 6454)
These two URLs have the same origin:
These URLs have different origins than the previous two:
Internet Explorer does not consider the port when comparing origins.
for more: http://www.asp.net/web-api/overview/security/enabling-cross-origin-requests-in-web-api
Also from Microsoft Web-API: http://www.asp.net/web-api/overview