|
|
Posted by Colin McKinnon on 03/20/06 23:37
bellefy@gmail.com wrote:
> I have, what I'd like to think as anyway, a unique situation.
>
> I have a client that has contracted me to build a custom inventory
> management system to be installed at the client's location. More
> specifically, a custom reporting display system through a kiosk-like
> linux installation using a locked-down FireFox.
>
> My development style has always been centralized around one primary
> class file (Kernel.php) that calls in the appropriate modules as
> needed.
>
> For example:
> $ php ./Kernel.php sendReport
>
It's a horrible way to build a system. Using a front-controller makes a
large PHP system much more difficult to write.
> Because this job is to be installed at the client location, is there a
> way that I can limit the entire installation of PHP to only allow
> Kernel.php to execute?
>
If that is really your objective then the shortest route to that goal would
be to rewrite the PHP or hack something terrible using an access control
system like RBACS.
I suggest you re-examine the problem and see if that is the right solution.
C.
Navigation:
[Reply to this message]
|