Re:ASP.NET You're doing it Wrong. An Introduction to Nancy
by mcgwiz on Wednesday August 21, 2013 @03:06PM
(#6252616)
How about a demonstration of something of real-world significance?
- content negotiation (basic building block of hypermedia APIs),
- authentication (and ensure SSL is used when authenticated),
- most importantly, HTTP caching, where
-- unauthenticated users get cached content, authenticated users don't,
-- vary on representation negotiations (media type, encoding, and language),
-- cache is located on server and in browser.
In other words, take basic advantage of HTTP to improve security and performance. Taken together, the requirements listed above comprise a problem of only moderate complexity, and are fundamental to flexible, high performance web apps. Accomplishing it in ASP.NET MVC/Web API is painful and relies on the inconsistent, malfunctioning, horrifically designed ASP.NET response caching module.
Show me a framework that does the above and makes it reasonable to build hypermedia APIs, and you've got yourself a convert.
- content negotiation (basic building block of hypermedia APIs),
- authentication (and ensure SSL is used when authenticated),
- most importantly, HTTP caching, where
-- unauthenticated users get cached content, authenticated users don't,
-- vary on representation negotiations (media type, encoding, and language),
-- cache is located on server and in browser.
In other words, take basic advantage of HTTP to improve security and performance. Taken together, the requirements listed above comprise a problem of only moderate complexity, and are fundamental to flexible, high performance web apps. Accomplishing it in ASP.NET MVC/Web API is painful and relies on the inconsistent, malfunctioning, horrifically designed ASP.NET response caching module.
Show me a framework that does the above and makes it reasonable to build hypermedia APIs, and you've got yourself a convert.