I'm having a remoting issue with Flex2 and ColdFusion. What I have is to
seperate sites on a single server, both of which are using remoting to access a
cfc. Each site has it's own copy of the CFC, located at the same path
(/webservice/flex/<componentName>.cfc), therefore, each site is using the same
path to access the cfc (webservice.flex.<componentName>).

The problem I am having is that the physical path to the CFC seems to be
cached. So for exampled, if site a accesses the CFC, the file at
C:\Inetpub\wwwroot\<sitea>\webservice\flex\<componentName>.cfc is access. When
Site B attempts to access it's copy of the CFC, it seems that CF (I'm assuming
this problem is occurring in CF) sees the path
"webservice.flex.<componentName>", which it has alredy served, and uses the
same physical path as before, when now it should be
C:\Inetpub\wwwroot\<siteb>\webservice\flex\<componentName>.cfc. I'm wondering
if anyone else has encountered this caching of path before, and if so, if
anyone knows how to prevent it from happening.

Thanks.

Ryan McIlmoyl

More information, it seems this information is being held in memory by
ColdFusion. After restarting the ColdFusion application server, this 'cache'
seems to be reset, and the path 'webservice.flex.<componentName>' will map to
the physical location of the next site to make a request.