ASP.NET Postbacks x jQuery: What are the cons and pros?
<p>I'll start some lab prototypes on some of our Web App pages. We use a lot of Postback, ViewState, UpdatePanels, ModalPopup Extenders, all the ASP.NET usual stuff. It's good enough for most cases. But I wanna push things further...</p>

<p>I've been playing around with jQuery for some time now. I know what's capable of. I'm thinking of TRULY substituting the ASP.NET usual things by things like <code>$.ajax()</code>, <code>$.get()</code>, etc. No more postbacks. User interface? jQuery UI. I'm truly impressed by some plugins, specially jQuery grid.</p>

<p>I think it's the next step into Web UI. I mean, it's ALREADY the current step! I love the power of C#, but I'm not that impressed with the ASP.NET framework. I imagine that by doing that, I'll truly separate UI from Business logic.</p>

<p>However:</p>

<ul>
<li>Should I really do it? </li>
<li>Should the code behind be only Web Handlers and Web Services? </li>
<li>What should I beware of?</li>
<li>How about security? How to implement it?</li>
<li>What will I gain? I know I'll gain some in performance, since postbacks in pages with too much data takes time because of the ViewState AND I'll be transacting only XML and/or the always light JSON format. But I imagine, as usual, there will be pain... </li>
<li>Where will the pain be?</li>
</ul>

<p>I'll take it slow, anyway. But I want to ask you guys: what am I getting into here?</p>
