ok -----Original Message----- From: "Jim McAtee" <[EMAIL PROTECTED]> To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com> Sent: 2/29/08 5:51 PM Subject: Re: Best practices in setting up a web site with IIS
From: "Reimer, Mark" > Question in setting up a website. We will be using IIS (this has > been decided by others, and I can't change it). > > Should subsites be: > > www.subsite.ourdomain.com > > or > > www.ourdomain.com/subsite > > Which is better practice? We will be spreading across multiple > servers, with each server hosting one or two subsites. > > If the latter, what the preferred way of setting things up so > the subsite gets pointed to the right server? The first approach is done in DNS, which is pretty straightforward. (BTW, I'm not sure about best practices, but I've never liked using 'www.subdomain.domain.com' host names. There's no reason to prepend the www. except where it's expected at the topmost level. People seldom type in these sub-host names manually, so are unlikely to add a www.) Can the second approach be used to actually offload application server load to another server? Wouldn't it be done up by creating a virtual directory in IIS and pointing it at a share on another server? This would only retrieve files from the second server, meaning any applications would still run on the main server. Or maybe there's another way to set it up, such as through a redirect. I've only ever used the first approach, never the latter. I'm not sure where the second would be desirable (or necessary), unless there are search engine optimization reasons. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
