Hi, Isaac... At this point, I was think that identifying the agent involved via the referring url or internally via a url variable would allow me to query a db for all needed variables, turn those variables into session variables, and then setup the agent pages via the session variables.
I don't know much anything much about isapi_rewrite (did find that ionic has a free version, but it's functionality with II6 is a bit sketchy...), however, that approach, using folders for each agent requires duplicate code and I was thinking that it would be more efficient to use the same code with different variables. However, that may not be true and the only thing being saved by taking the code-reuse route would be server space. To clarify your statement about application.cfm... Are you suggesting putting an application.cfm in the main agents folder, and then having an application.cfm in *each* of the specific agents' folders and simply have that "included" application.cfm contain the specific variables needed an agent? So, that's preferable to just using one application.cfm in the main "agents" folder and determining the agent to use via cgi.server_name or url variables and a series cfif's and queries? Rick > -----Original Message----- > From: s. isaac dealey [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 08, 2008 11:29 AM > To: CF-Talk > Subject: Re: Need some advice on approach... > > Hey Rick. > > Brief recommendation. You mentioned you're using Application.cfm still - > what you might want to do is add an Application.cfm in your /agents > subdirectory to modify whatever the original Application.cfm did to > set up the page... > > /root/Application.cfm > .... original code ... > > /root/agents/Application.cfm > <cfinclude template="../Application.cfm"> > .... change paths if necessary, etc ... > > That way you don't need to check for the subdomain to see if they're > coming to one... you know, 'cause they're in that directory... however > fitting them into that directory is another story. You can of course set > up an a-record(?) for each agent that points to their directory, but > that's a lot of configuration (or I would expect it to be) - my bet > would be to use either mod_rewrite on Apache or isapi_rewrite on IIS to > change the URL based on a rule, so that as far as the server is > concerned any request to [not www].c21ar.com is actually to > www.c21ar.com/agents/?subdomain=[not www] or to > www.c21ar.com/agents/[not www]/ depending on how you structured it -- > I was a little fuzzy on the details. :) > > hth > > > -- > s. isaac dealey ^ new epoch > isn't it time for a change? > ph: 617.365.5732 > > http://onTap.riaforge.org/blog > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307055 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
