<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Separating Web Container from Application Container</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Thu, 23 May 2013 11:18:20 -0400</pubDate>


    <item>

        <title>Reverse Proxy</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[The most intersting in security point of separating .. is proxying  many application container with one web container and this one can operate as 'HTTP broker' , you can hide the internal server name and client never think he deal with the real hidden...]]></description>
        

        <pubDate>Thu, 09 Mar 2006 06:36:56 -0500</pubDate>

        

        <jf:creationDate>Thu, 09 Mar 2006 06:36:56 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 09 Mar 2006 06:36:56 -0500</jf:modificationDate>
        <jf:date>Mar 9, 2006</jf:date>
        <jf:author>A A</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>It depends</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[I totally agree. I was referring to an intranet case.<br>There should be a separate web server in the DMZ and that is mandatetory for the most case, for security reasons.]]></description>
        

        <pubDate>Mon, 27 Feb 2006 04:30:48 -0500</pubDate>

        

        <jf:creationDate>Mon, 27 Feb 2006 04:30:48 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 27 Feb 2006 04:30:48 -0500</jf:modificationDate>
        <jf:date>Feb 27, 2006</jf:date>
        <jf:author>Akira Yamazaki</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>It depends</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[It basically depends whether your app is intranet or publically facing internet. <br><br>In case of a small department-wide intranet app you might be able to get away with colocating the web and EJB containers.<br><br>If your app is public, you most...]]></description>
        

        <pubDate>Fri, 24 Feb 2006 21:37:28 -0500</pubDate>

        

        <jf:creationDate>Fri, 24 Feb 2006 21:37:28 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 24 Feb 2006 21:37:28 -0500</jf:modificationDate>
        <jf:date>Feb 24, 2006</jf:date>
        <jf:author>Andre Mesarovic</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Separating Web Container from Application Container</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[<blockquote>... Router/Firewall server that protects and load balances between servers(where web and app containers are in same process on each server) I can see security being met while keeping the web and app containers together.</blockquote><br>Here...]]></description>
        

        <pubDate>Thu, 23 Feb 2006 09:13:19 -0500</pubDate>

        

        <jf:creationDate>Thu, 23 Feb 2006 09:13:19 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 23 Feb 2006 09:13:19 -0500</jf:modificationDate>
        <jf:date>Feb 23, 2006</jf:date>
        <jf:author>Akira Yamazaki</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Separating Web Container from Application Container</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[Thanks for the feedback.  I was wondering though, if you have an architecture (rough picture below) where you have Router/Firewall server that protects and load balances between servers(where web and app containers are in same process on each server) I...]]></description>
        

        <pubDate>Wed, 22 Feb 2006 20:32:10 -0500</pubDate>

        

        <jf:creationDate>Wed, 22 Feb 2006 20:32:10 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 22 Feb 2006 20:32:10 -0500</jf:modificationDate>
        <jf:date>Feb 22, 2006</jf:date>
        <jf:author>Logan Kiefer</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Separating Web Container from Application Container</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[Well, it's just my experience you'd better to have a separate configuration to limit access the site. Usually this configuration is in a Web server. If site accesses is going to be a small or not so fractuated, you may not need a separate configuration...]]></description>
        

        <pubDate>Tue, 21 Feb 2006 19:29:23 -0500</pubDate>

        

        <jf:creationDate>Tue, 21 Feb 2006 19:29:23 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 21 Feb 2006 19:29:23 -0500</jf:modificationDate>
        <jf:date>Feb 21, 2006</jf:date>
        <jf:author>Akira Yamazaki</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>Separating Web Container from Application Container</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[Good Point. If you display a lot of static pages this can be useful.  However would you agree if almost every request is dynamic (needs business logic and database info) then there is not really a need to separate the two?]]></description>
        

        <pubDate>Tue, 21 Feb 2006 13:17:19 -0500</pubDate>

        

        <jf:creationDate>Tue, 21 Feb 2006 13:17:19 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 21 Feb 2006 13:17:19 -0500</jf:modificationDate>
        <jf:date>Feb 21, 2006</jf:date>
        <jf:author>Logan Kiefer</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>


    <item>

        <title>Separating Web Container from Application Container</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[If you have a web server separated from an app container, the web server can concentrate on processing static page requests which would normally be a large part of web accesses.<br>If a site has very tiny web application or less possibility for visitors...]]></description>
        

        <pubDate>Mon, 20 Feb 2006 06:41:38 -0500</pubDate>

        

        <jf:creationDate>Mon, 20 Feb 2006 06:41:38 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 20 Feb 2006 06:41:38 -0500</jf:modificationDate>
        <jf:date>Feb 20, 2006</jf:date>
        <jf:author>Akira Yamazaki</jf:author>
        <jf:replyCount>6</jf:replyCount>
    </item>


    <item>

        <title>Separating Web Container from Application Container</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39086</link>

        

        
            <description><![CDATA[What would be good reasons to have the web and app container in separate processes?  <br><br>From a scalability stand point if both were in the same process you can scale both apps in that same process either vertically or horizontally.  Separating them...]]></description>
        

        <pubDate>Sat, 18 Feb 2006 18:38:26 -0500</pubDate>

        

        <jf:creationDate>Sat, 18 Feb 2006 18:38:26 -0500</jf:creationDate>
        <jf:modificationDate>Sat, 18 Feb 2006 18:38:26 -0500</jf:modificationDate>
        <jf:date>Feb 18, 2006</jf:date>
        <jf:author>Logan Kiefer</jf:author>
        <jf:replyCount>8</jf:replyCount>
    </item>



</channel>
</rss>

