Vitaliy Babiy wrote:
Hello folks
I am starting a new project today which is going to have more 200 run modes, and I would
like to break things up.
Good idea.
But I'd like to have single CGI script that handles every request to the
application.
I also need to have centralized list of all run
I am starting a new project today which is going to have more 200 run
modes, and I would
like to break things up.
But I'd like to have single CGI script that handles every request to the
application.
I also need to have centralized list of all run modes from every module.
I'm going to have some
On Thu, 22 Jul 2004, Vitaliy Babiy wrote:
I am starting a new project today which is going to have more 200
run modes, and I would like to break things up.
But I'd like to have single CGI script that handles every request to
the application. I also need to have centralized list of all run
Hello folks
I am starting a new project today which is going to have more 200 run modes, and I
would
like to break things up.
But I'd like to have single CGI script that handles every request to the application.
I also need to have centralized list of all run modes from every module.
I'm
I am starting a new project today which is going to have more 200 run
modes, and I would
like to break things up.
Next. I suppose I will have one base class which will be called form
CGI script.
This class will have only one run-mode, which will load config and
determine, which module to load
On Thu, 22 Jul 2004 23:04:38 -0400, Vitaliy Babiy wrote:
Hi Vitaliy
I am starting a new project today which is going to have more 200
run modes, and I would
200!
But do you really need that many?
I have written a search engine for a university department/staff/phone
database whose main
