Came across this post at Dave Ward’s blog, and I walked away with mixed emotions about it. Don’t get me wrong — it’s definitely a good concept: making a page more responsive is always great. And I heartily recommend checking it out too. But his example is highly .NET specific (and the example C# does rely on 3.5 stuff too, so keep that in mind).
There’s nothing wrong with that; just my personal preferences keep me relying less on ASP.Net AJAX, trying to work more with a more “natural” JavaScript library like Prototype. I mean, I highly doubt that I’ll start porting my projects to Ruby on Rails or PHP or anything else that would require a non-.NET related JS library, but still…
Anyways, the concept he states is a good one: for (some) static content, use AJAX to load it dynamically instead of having the rest of your page wait for it. Pretty simple, huh?
Maybe when I get bored this weekend, I’ll extrapolate it to Prototype.
Posted by: mcory
Posts that may or may not be similar to the above:
- Ground-Up ASP.Net Development I: At the…Well…Ground.
- Quickie: Unit Testing Asp.Net
- Visitor Pattern: One Fix for LSP Violations
- Some Goodies: Model-View-Presenter Article, Java in .NET, HtmlUnit
- OOD Principles I: Liskov Substitution Principle
Categories: