Hi,

trying to think through running an app in two(or more) versions side by side
on the server.

Currently we always instanstiate a component using a string that adds a
unique prefix (corresponding to a cf mapping - and a mapping in the web.xml
file to cater for webservices)

This approach is fine until I want to extend other cfcs that are not in the
same folder, as this is a compile time directive and thus doesn't support
dynamic values.

If each version runs out of a seperate webserver instance (IIS) I can set a
virtual directory which has the same name for each site but references the
particular component directory for that site.


On IIS in XP pro I can only have one website so this is a little problem - I
can install Apache of course (though as an aside my CF wont then work on
BD.Net, as ASP.Net requires IIS). Of course I can install a server, and in
staging and production it will alwatys be Full IIS.

Just wondered how people are hadling these sorts of issues with concurrent
versions etc.

Elliot




---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to