|
When I came from ACF to OpenBD, my first urge was to create an
"Adobe-like" setup, in which one monster CF engine powered all my CF
apps. After a while, I realized that the OpenBD war was so lightweight that the problems were all in my head. Now I just deploy one OpenBD engine-per-app and things are surprisingly easier, especially in the pathing and cgi vars department. I don't know how many of us do it one way vs the other. I'm not sure if this addresses anything in your case, or even helps. But recent talk of documentation and manuals made me want to comment that there's little there - to suggest that developers try to shift their way of thinking when they move to OpenBD: When it's free, you can just encapsulate one app per war deployment. FWIW I think Railo tends to follow the classic ACF multi-app setup in their design... at least in their administrator. Al -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en |
- [OpenBD] Connector bridge of proxyin... Ivo Verbeek
- Re: [OpenBD] Connector bridge o... Alex Skinner
- Re: [OpenBD] Connector brid... Alan Holden
- [OpenBD] Re: Connector ... Ivo Verbeek
- Re: [OpenBD] Re: Co... Alan Williamson (aw2.0 cloud experts)
- [OpenBD] Re: Connector brid... Ivo Verbeek
- [OpenBD] Re: Connector brid... Ivo Verbeek
