Forgive the delayed response... Not all content on my server is cfml. Some is plain html and there's also some php from the traditional LAMP setup. For the few cfm files that a user actually browses, I did not want to have the funky 8400 port as part of the url. Being a total noob, I was just following Nitai's instructions here: http://blog.openbluedragon.org/video_apache.htm
Regarding your other questions - about the optimal setup for using openBD / tomcat for a scalable provider of high volume cfc data calls - I'm looking for the same answer myself. I'm hoping that someone (much smarter than I) would anoint my /assumption/ that one should use a wsdl path direct to the IP and port of the openBD app on tomcat; and bypass both the DNS translation step and the apache proxy step as well. Since users would hardly ever see wsdl paths, they need not be pretty. I imagine BlazeDS would be an even faster and better answer to your scalability issues (but I could never get Matt's demo to work on my setup). You can read my whining about that on a different thread: "OpenBD & BlazeDS turnkey download" Al Tom Jones wrote: > I have been wondering, why not just use tomcat to serve up all of the > data? > (snip) --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
