Did you guys know that you can define a mapping that looks like this
"/com/domain"? This way, you don't have to worry about mapping to "/com"
because you aren't.
If your directory structure is like this:
+-root
+-cfc
| +-util
| | +-foo.cfc
| | +-bar.cfc
| +-ui
| +-button.cfc
+-includes
+-app1
and you have a the following mapping:
PHYSICAL LOGICAL
"/root" ==> "/com/domain"
you can name/call components as below:
PHYSICAL LOGICAL
"/root/cfc/util/foo.cfc" ==> "com.domain.cfc.util.foo"
"/root/cfc/util/bar.cfc" ==> "com.domain.cfc.util.bar"
"/root/cfc/ui/button.cfc" ==> "com.domain.cfc.ui.button"
Anyhow, this is how I get around this entire issue in a hosted environment.
Paul Kenney
WebMaster, CorporateWarriors.com
[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Jim Davis
Sent: Thursday, December 04, 2003 1:48 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] Including CFCs relatively - THE SOLUTION
I'm not sure... I was bitten bad by this a while ago. I created a directory
"com.depressedpress.cfcs" and everything worked with no mapping... then
somebody must have mapped "com" because my app was toast.
I think that your assumption is correct however: in a shared environment no
mappings are better (at least if each site has it's own webroot) as the
webroot discovery should work.
But if your host does allow mappings to be requested (many do) then it seems
like you can be blown out of the water at any time whatsoever.
The problem right now is that all the hosts are struggling with this - and
everyone is coming up with their own solutions. We've got a mess. A set of
Macromedia-supported best practices for this would have helped a lot.
Jim Davis
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Ben Curtis
> Sent: Thursday, December 04, 2003 4:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [CFCDev] Including CFCs relatively - THE SOLUTION
>
>
> > I think the problem that a lot of us have is that in a hosted
> environment
> > (shared server) you rarely have any access to the administrator. Also,
> even
> > if you do since you're in a shared environment only one user can create
> any
> > specific mapping - so if two users try to set up the same application
> they
> > may conflict.
>
> So the reason I don't experience this problem in my shared
> hosting environment is because we have specified no mappings
> whatsoever, and therefore we can code our cfc paths from the
> web root without any overlapping of names, etc.? If that's
> the case, why use mappings at all, ever?
>
> --
>
> Ben Curtis
> WebSciences International
> http://www.websciences.org/
> v: 310 478 6648
> f: 310 235 2067
>
>
>
>
>
>
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email
> to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
> in the message of the email.
>
> CFCDev is run by CFCZone (www.cfczone.org) and supported
> by Mindtool, Corporation (www.mindtool.com).
>
> An archive of the CFCDev list is available at www.mail-
> archive.com/[EMAIL PROTECTED]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[EMAIL PROTECTED]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
