You shouldn't have any problems. An SSL certificate is tied to a domain
name so you could even run the sites on the same IP address, but I
wouldn't because there are still some things out there which don't
support HTTP 1.1 (namely a few search engines).
In fact, a few applications I've designed recently do this. I basically
look at the CGI scope to determine which site was requested and create a
ColdFusion application dynamically (I do love that kind of versatility
in ColdFusion).
Giving each site it's own application ensures that if the customer
uploads any custom pages to a directory I've created for that purpose,
they won't accidentally step on another site's application, session and
client vars. The directory structure looks something like:
./ Root of the web site. This directory (and its
sub-directories) contains the code which is
shared amongst all the sites. The exception
is the sites directory.
./sites All custom files uploaded by the client are
kept in a sub-directory of this directory.
./sites/1 Each individual site's files are kept in a
./sites/2 directory with a unique identifier which
./sites/3 corresponds to a value in the database. If a
file exists in one of these directories with
the same name as file in the root directory
of the site, then that file is used instead
of the file in the root directory.
This all adds a marginal amount of overhead, of course, but it is very
reasonable. I don't have any exact numbers. I had a performance
bottleneck in one application that I was working on last week, but it
turned out to be something unrelated to the site framework.
One downside is sandboxing. Sandboxing is based on the directory the
code resides in. So, you have to give the root sandbox access to all the
applications. However, *I believe* I could create sandboxes for each
site's custom files and lock those down a bit tighter than the root
sandbox. I haven't tried this yet, though.
Benjamin S. Rogers
http://www.c4.net/
v.508.240.0051
f.508.240.0057
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Saturday, August 16, 2003 6:01 PM
To: cfczone
Subject: [CFCDev] OT: Different domains/hosts to same
code base
I have weird scenario, am trying to use the same code base for
different sub-domains/host names (Affiliates) and they should be
on SSL, depending the on sub-domain, the MVC (VIEW) Compoents
change
but the Model and Data Layers stay the same and i want BOTH
SSL's to point the same directory.
Example..
Company ABC (https://secure.abc.com) and Company XYZ
(https://secure.xyz.com)
both secure need to point to one directory (affliateAuth),
depending on the domain i
can set some request parameters and switch out View Compoents
(e.g view/abc and view/xyz)
This application specific stuff is clear, am wondering if there
are goona be any issues with
the SSL for 2 different domains and 2 different IP Address
pointing the same directory.
Basically, am trying Not to replicate code by doing all the
above.
Appreciate any input.
Joe Eugene
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
