<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:copyright="http://blogs.law.harvard.edu/tech/rss" xmlns:image="http://purl.org/rss/1.0/modules/image/">
    <channel>
        <title>ASP.NET</title>
        <link>http://geekswithblogs.net/gefest/category/2989.aspx</link>
        <description>ASP.NET</description>
        <language>en-US</language>
        <copyright>Michael Kalika</copyright>
        <managingEditor>Michael.Kalika@GMail.com</managingEditor>
        <generator>Subtext Version 0.0.0.0</generator>
        <item>
            <title>ASP.NET 2.0 Provider Model</title>
            <link>http://geekswithblogs.net/gefest/archive/2005/10/18/57282.aspx</link>
            <description>Microsoft has published the following articles about their ASP.NET 2.0 provider model: &lt;BR&gt;&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/ASPNETProvMod_Intro.asp" target=_blank&gt;Introduction to the Provider Model&lt;/A&gt; (14 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt1.asp" target=_blank&gt;Membership Providers&lt;/A&gt; (24 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt2.asp" target=_blank&gt;Role Providers&lt;/A&gt; (13 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt3.asp" target=_blank&gt;Site Map Providers&lt;/A&gt; (20 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt4.asp" target=_blank&gt;Session State Providers&lt;/A&gt; (21 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt5.asp" target=_blank&gt;Profile Providers&lt;/A&gt; (23 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt6.asp" target=_blank&gt;Web Event Providers&lt;/A&gt; (14 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt7.asp" target=_blank&gt;Web Parts Personalization Providers&lt;/A&gt; (12 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt8.asp" target=_blank&gt;Custom Provider-Based Services&lt;/A&gt; (10 printed pages)&lt;BR&gt;&lt;A href="http://msdn.microsoft.com/library/en-us/dnaspp/html/ASPNETProvMod_Prt9.asp" target=_blank&gt;Hands-on Custom Providers: The Contoso Times&lt;/A&gt; (3 printed pages) &lt;img src="http://geekswithblogs.net/gefest/aggbug/57282.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>Michael Kalika</dc:creator>
            <guid>http://geekswithblogs.net/gefest/archive/2005/10/18/57282.aspx</guid>
            <pubDate>Tue, 18 Oct 2005 18:54:00 GMT</pubDate>
            <wfw:comment>http://geekswithblogs.net/gefest/comments/57282.aspx</wfw:comment>
            <comments>http://geekswithblogs.net/gefest/archive/2005/10/18/57282.aspx#feedback</comments>
            <wfw:commentRss>http://geekswithblogs.net/gefest/comments/commentRss/57282.aspx</wfw:commentRss>
            <trackback:ping>http://geekswithblogs.net/gefest/services/trackbacks/57282.aspx</trackback:ping>
        </item>
        <item>
            <title>AJAX - To use or not to use</title>
            <link>http://geekswithblogs.net/gefest/archive/2005/10/16/57153.aspx</link>
            <description>I just read &lt;A href="http://weblogs.asp.net/Plip" target=_blank&gt;Plip's&lt;/A&gt; post about &lt;A href="http://weblogs.asp.net/plip/archive/2005/10/16/427624.aspx" target=_blank&gt;Ajax and usability&lt;/A&gt;.&amp;nbsp;Recently, there is a lot of buzz around AJAX technology. To use or not use -&amp;nbsp;that is the question. I think it's OK and even a good practice to mix AJAX with a&amp;nbsp;non-AJAX code for scenarios like datetime picker that depends on the server date and time, querying for something on the server every specified interval of time (for some alert for example), parent/child relationship between lists and/or comboboxes, perform some action on server when user closes the window and so on. AJAX will save all the roundtrip to the server and improve experience of your users. But you should use it wisely. I wouldn't build a whole application with AJAX until it&amp;nbsp;become transparent to our users (I mean problems with&amp;nbsp;back, refresh, stop buttons and so on). &lt;img src="http://geekswithblogs.net/gefest/aggbug/57153.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>Michael Kalika</dc:creator>
            <guid>http://geekswithblogs.net/gefest/archive/2005/10/16/57153.aspx</guid>
            <pubDate>Mon, 17 Oct 2005 02:12:00 GMT</pubDate>
            <wfw:comment>http://geekswithblogs.net/gefest/comments/57153.aspx</wfw:comment>
            <comments>http://geekswithblogs.net/gefest/archive/2005/10/16/57153.aspx#feedback</comments>
            <slash:comments>1</slash:comments>
            <wfw:commentRss>http://geekswithblogs.net/gefest/comments/commentRss/57153.aspx</wfw:commentRss>
            <trackback:ping>http://geekswithblogs.net/gefest/services/trackbacks/57153.aspx</trackback:ping>
        </item>
    </channel>
</rss>
