Rethink the way you plan, design, and build Web applications with expert guidance from Web development luminary Dino Esposito. Whether giving legacy sites a much-needed tune-up or architecting rich Internet applications from the ground up you ll learn pragmatic approaches to AJAX development that you can employ today. Discover how to: Delve into the mechanics and design goals of partial rendering such as improving page-refresh speed Use AJAX-enabled server controls to bring desktop-like functionality to Web solutions Apply design patterns to common Web development issues, including client-side data binding Manipulate JavaScript more easily using the jQuery and Microsoft AJAX libraries Examine the interoperability and security models in Microsoft Silverlight Weigh the tradeoffs when architecting Web applications for richness (Silverlight) vs. reach (AJAX) and deliver the right solution for your audience
Microsoft® ASP.NET and AJAX: Architecting Web Applications (PRO-Developer)
- Authors
- Dino Esposito
- ISBN
- 0735626219
- Published
- 15 Apr 2009
- Purchase online
- amazon.com
Now s the time says Dino Esposito, an expert on Web development technologies to think about AJAX and the future of Web design in a whole new way. While developers can use a variety of tools to code and build AJAX applications, architects must manage a variety of tradeoffs and compromises in their planning and design. In this book, Esposito challenges readers to think beyond the easy way to AJAX, which involves adding AJAX capabilities to a non-AJAX system designed in the old model of Web devel
Editorial Reviews
You might also like...
ASP.NET books
-
Dynamic Web Application Development with ASP.Net (Computing)
This is the latest book from Cengage Learning on "Dynamic Web Application Development with ASP.NET...
ASP.NET podcasts
-
Hanselminutes: Startup Series: Buying an Existing Small Company or Online Application
Published 8 years ago, running time 0h34m
Scott talks to Rob Walling about how he purchases small niche products and companies online and revitalizes them. He recently purchased an existing product that consisted of a 300 gig database and tens of thousands of lines of Classic ASP. How did he know it was valuable? What's next?
Comments