MACROMEDIA COLDFUSION STUDIO 5-USING COLDFUSION 5 STUDIO Use Manual page 39

Working with Files on Remote Servers
For example, a user might have a remote drive X:\ mapped to a network shared
directory \\MYSERVER\WEBPROJECTS\ where WEBPROJECTS is the name of the
shared directory in the network server MYSERVER.
In such a scenario, a file that appears to Studio as
X:\App1\index.cfm
might be viewed by the server as
C:\webprojects\App1\index.cfm
and the browser might view it using the URL
http://215.180.21.1/App1/index.cfm
In order to resolve the communication between Studio and Server, you must create a
mapping for the App1 directory as follows:
Studio access to a remote server using drive mappings
Studio path
Server path
Browser/URL path
Using UNC paths/Network Neighborhood
Developers can debug code against remote ColdFusion servers across an internal
network using
on a remote server. For example, a developer might access a file on
\\myserver\webprojects\ where webprojects is the name of the shared directory in
the network server myserver.
In such a scenario, a file that appears to Studio as
\\myserver\webprojects\App1\index.cfm
might be viewed by the server as
c:\webprojects\App1\index.cfm
and the browser might view it using the URL
http://215.180.21.1/App1/index.cfm
Studio and Server need to understand how a file location appears to the parties
involved. You therefore must create a mapping for the App1 directory as follows:
Studio accesses files on remote server using UNC paths/Network
Neighborhood
Studio path
Server path
Browser/URL path
X:\App1\
C:\webprojects\App1\
http://215.180.21.1/App1/
UNC paths. They often use the Network Neighborhood to access a file
\\MYSERVER\WEBPROJECTS\App1\
C:\webprojects\App1\
http://215.180.21.1/App1/
path
path
21