On Nov 7, 2006, at 1:50 PM, Aparajita Fishman wrote:
Is it possible to still retain these old web apps, but develop new
web apps in fusebox? I ask because there are fusebox settings in
Active4D.ini, which makes me think that fusebox is "global", i.e.,
you either use it everywhere or not at all?
Unfortunately in the current incarnation of Active4D there is no
way to have per-virtual-host settings. But you can achieve the same
effect as the "fusebox page" setting using the On Request event
handler.
I've implemented a "virtual-host" fusebox site that coexists with a
traditional site. As Aparajita stated, you have to control what
happens with the "On Request" event handler. Basically you just have
to parse the results of $hostname := get request info("*host") and
return a URL that goes to the right web root driver (/index.a4d in
case of a fusebox site)
The only thing that does not appear to work is that fuse libraries
are not automatically loaded (and they have to be defined in "lib
dirs"). I think this is because I don't have "fusebox page" set in
the .ini file. Since my old site is still my major site, I have not
experimented with setting this value to the fusebox site and seeing
if "On Request" still functions for the old site. I have some logic
trying to make pretty URL in on request that will probably have to be
tweaked before I try. Think there were a few other problems with
identifying "special" files to be directly executed. The pretty URL
stuff resulted in multiple drivers - those had to be included on the
special side of the fusebox site ini setting.
Other than having to manually identify the libraries, the sites
coexist without any problem. I'll experiment this weekend and see if
I can get the fusebox page set and still have the traditional site
functional.
Steve Alex
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
