Not a problem... Think of it this way... an alias is a fakeName for a particular directory that you want to make available. It can't exist without a parent container: a vhost (or the default server.) So from CF's perspective, an alias is no different that any old folder in the various paths available to it from within the context of the current vhost container.
Once you realize that you can create any number of vhosts and only attach the Jrun connector to the ones that will utilize CF, or configure any number of them to use mod_proxy and mod_rewrite to utilize any CF server you have access to, it becomes apparent that CF really IS aware of the context provided by a vhost configuration. It actually doesn't even matter if you have vhosts in addition to the default server... in that case Apache treats the default server as just another vhost. Because the jrun connector is attached on a per-host basis and a vhost is effectively treated as an independent host, it must have it's own connector config. Thus, when CF asks Apache for the webroot of the current *host*, apache replies with the *vhost* value pointing to the folder designated as DocumentRoot in that vhost config. Hope that helps, I know Apache, CF, and any other intense server systems can be daunting and hard to configure... come on back if you still have questions. Laterz! J On Thu, 17 Mar 2005 00:11:53 -0400, Cliff Meyers <[EMAIL PROTECTED]> wrote: > >Since aliases can't exist outside a server config of some sort, an > >alias (apache) or a virtual directory (IIS) will look in the webroot > >of the site to which it is attached. > > Thanks for responding! So just to make sure I'm clear on what you mean, > going back to my prior example... > > (vhost) http://www.test.com -> /sites/site1 > (alias) http://www.test.com/othersite -> /sites/site2 > > If I make a call like: > > createObject("component","SomeFramework.SomeComponent") > > from within the context of "/othersite" it means that ColdFusion will be > "smart enough" to look here for my CFC? > > /sites/site1/SomeFramework/SomeComponent.cfc > > I can drop MachII in my custom tags folder and (as you'd expect) CF can > always find it, but if I want to write two separate apps and have them share > CFCs between the two it'd be convenient to if CF did have the functionality > I described... > > Thanks again! > > > -Cliff -- Continuum Media Group LLC Burnsville, MN 55337 http://www.web-relevant.com http://www.web-relevant.com/blogs/cfobjective ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:199075 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
