Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Wed, 21 Oct 2009 19:36:13 -0500
Subject: RE: Subdomains and Wars...
Thread-Topic: Subdomains and Wars...
Thread-Index: AcpSjWd8pGFII0SLQJucjZ1IUgwCBQAHyCyg
Message-ID: 
 <99C8B2929B39C24493377AC7A121E21F84059962F1@USEA-EXCH8.na.uis.unisys.com>
References: 
 <99C8B2929B39C24493377AC7A121E21F8405995FD4@USEA-EXCH8.na.uis.unisys.com>
 <792878.51186.qm@web39802.mail.mud.yahoo.com>
In-Reply-To: <792878.51186.qm@web39802.mail.mud.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> From: Tony Anecito [mailto:adanecito@yahoo.com]
> Subject: RE: Subdomains and Wars...
>=20
> I would have agreed if not for an admin asking about what if a file
> like a jpg was deployed via a war?

It makes no difference.

> I would say the developer should not have static content delivered=20
> via war to a app server but that is the way some dev groups deliver
> content.

??? Why not include the related static content with the webapp?  Doing othe=
rwise makes deployment much more complicated.  Just because a resource is s=
tatic doesn't mean it won't change from one release to another.  Bundle it =
all together; the servlet spec encourages self-contained webapps.

> With that in mind how would you expect the content for the http feature
> of Tomcat or even APR to be deployed?

Again, using what you call "subdomains" (it's really aliases) is irrelevant=
 to the server.  As long as the DNS entries exist to route all the aliases =
to the same server, and *your* webapp uses the aliases in the proper places=
, nothing is required of the server.

For example, if you have a web page named index.html from the default webap=
p at www.mydomain.org, and that page has some images and a style sheet, and=
 you have DNS entries for www.mydomain.org, img.mydomain.org, and css.mydom=
ain.org that all lead to the same server, you can do the following:

1) deploy your webapp as ROOT.war under the default <Host> appBase director=
y

2) put index.html in the base directory of ROOT.war

3) put the images wherever you want within the ROOT.war, base directory or =
somewhere else

4) put the style sheet wherever you want within the ROOT.war

(For the sake of discussion, we'll just leave all this in the base director=
y.)

5) in the index.html file, put the links to the images as http://img.mydoma=
in.org/img*.jpg, where the asterisk is the image number

6) in the index.html file, put the link to the style sheet as http://css.my=
domain.org/stylesheet.css

Magically, the browser will initiate concurrent requests for multiple image=
s and the style sheet, simply because the host names *appear* to be for dif=
ferent servers.  Really, there's no magic here - it's all just tricking the=
 browser into ignoring the RFC-recommended limit of two simultaneous connec=
tions to a given host.

And again, there's no server configuration required.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL and is thus for use only by the intended recipient. If you received =
this in error, please contact the sender and delete the e-mail and its atta=
chments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org