<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://ramin-tavassoli.de/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://ramin-tavassoli.de/feed.php">
        <title>tawiki csharp:aspnet</title>
        <description></description>
        <link>http://ramin-tavassoli.de/</link>
        <image rdf:resource="http://ramin-tavassoli.de/lib/tpl/dokuwiki/images/favicon.ico" />
       <dc:date>2026-04-29T18:48:45+02:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:mvc&amp;rev=1371989380&amp;do=diff"/>
                <rdf:li rdf:resource="http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:webapi&amp;rev=1371991484&amp;do=diff"/>
                <rdf:li rdf:resource="http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:webforms&amp;rev=1371987876&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://ramin-tavassoli.de/lib/tpl/dokuwiki/images/favicon.ico">
        <title>tawiki</title>
        <link>http://ramin-tavassoli.de/</link>
        <url>http://ramin-tavassoli.de/lib/tpl/dokuwiki/images/favicon.ico</url>
    </image>
    <item rdf:about="http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:mvc&amp;rev=1371989380&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-06-23T14:09:40+02:00</dc:date>
        <title>csharp:aspnet:mvc</title>
        <link>http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:mvc&amp;rev=1371989380&amp;do=diff</link>
        <description>The Model View Controller paradigm very nicely separates the web server layer into the different regions of responsibility. Unlike in ASP.NET Web Forms, the object model, controller logic and presentation logic don't get hopelessly mixed up.

	&quot;&quot;

Still, there is too much business logic in classic controllers for my taste. The web server should be there merely for presenting an already existing model, and for passing through commands to change that model to an existing application layer.</description>
    </item>
    <item rdf:about="http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:webapi&amp;rev=1371991484&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-06-23T14:44:44+02:00</dc:date>
        <title>csharp:aspnet:webapi</title>
        <link>http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:webapi&amp;rev=1371991484&amp;do=diff</link>
        <description>ASP.NET Web API is the applications remote facade. It can be used in process, for example by an ASP.NET MVC application running in the same domain, exposing views to browsers, or it can be used remotely, for example by an httpClient inside a Windows Forms application or from inside the browser via AJAX calls.</description>
    </item>
    <item rdf:about="http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:webforms&amp;rev=1371987876&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-06-23T13:44:36+02:00</dc:date>
        <title>csharp:aspnet:webforms</title>
        <link>http://ramin-tavassoli.de/doku.php?id=csharp:aspnet:webforms&amp;rev=1371987876&amp;do=diff</link>
        <description>DON'T USE. Use ASP.NET MVC instead.</description>
    </item>
</rdf:RDF>
