On 10/16/07, Michael E. Carluen <[EMAIL PROTECTED]> wrote:
>
> > I could be wrong, but I don't think IIS supports wildcard sites. Which
> > is too bad, because that's actually a very elegant solution.
True that, now that I ready this, it would be really cool. I have an
application I'm working on right now that would be banging for something
like this, but I would think it's more of an issue getting the dns
propagated that's half the problem. it takes less time to setup a subdomain
in IIS than creating one through a control panel at your hosting company or
registrar.
Out side of this Jessica, <cfset TheDomain = "#CGI.SERVER_NAME#"> and then
doing a call against your database user table for such domain does work.
This even allows you to offer custom domain names. xyzhomesforsale.com could
bring up the same application as abchomesforsale.com using this method and
checking for the servername.
When the visitor first hit's the server from a unique domain name, or
subdomainname.com I set the ApplicationName to something from the database
or just use their domain. I guess you could use CGI.QUERY_STRING if you
need to get the info that way. I would just recommend setting up subdomains,
to the point where the information displayed is exactly the same. If this is
the case, SEO rule 1 is don't duplicate content so having 100 domains
displaying the same 400 listings is going to look funny to google.
So in application.cfc
<cffunction name="onApplicationStart">
HomesApp_#ReturnedQueryDomain.ClientIDDigits#
</cffunction>
I now know that everything from this point forward is going to be inline
with the clients domain and no one else's. Everything else can be set or gat
because of this initiall check and the setting of variables in the
application scope. This includes things like where to store images and how
records are displayed. If you always run the domain/id check along with your
queries. the visitor should always only receive the currents domains
information.
getlistings.cfm
<cfscript>
listing = StructNew();
listing.ID = URL.listingID;
listing.Client = APPLICATION.homesConfig.ClientIDDigits;
rsHomeListings = APPLICATION.cfc.HomeListings.getListing
(argumentCollection=listing);
</cfscript>
<cfoutput query="rsHomeListings ">
</cfoutput>
Of course they are more parts to this but the only downside I've seen so far
is refreshing application scope it's self across all applications without
rebooting the box.
So far it seems like loading pages with cfhttp is the best way to go about
this. I figure refreshing the applications is the least of my worries, but
maybe I'm wrong when there could be 100 or 1000 + applications running.
Maybe someone else has a better way of refreshing all applications on a
server.
Casey
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion 8 - Build next generation apps
today, with easy PDF and Ajax features - download now
http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:291291
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
