Not that anybody cares... but the old acf did this:
Which was cool, but... what the heck was it doing?!!!
Turns out, mvc:new was figuring out the application name on its own,
loading application code, and all kinds of interesting things (that it
probably should not have been doing)
Here's a sample of the new code in acf:
#!/usr/bin/haserl --shell=lua -a
-- create a new container. This container will contain
-- application level configuration params, but not code
-- load the container with the config info, using "acf" as
-- the applciation name
-- Create an application container (this time, the "acf"
-- controller/model code will be loaded)
-- And dispatch it
So, FRAMEWORK has acf .conf, but not .worker and .model
APP has acf's .worker and .model
question: Does anyone care about the extra FRAMEWORK table? It was
there in the orignal case, but it was hidden from view. This just makes
I'm assuming the answer is "no"
Received on Thu Mar 01 2007 - 15:00:43 GMT