Thought I'd chime in here:
On my "to-do" list is a master that will allow per-thread
module/program/include paths. I hope to get that working in the next few
months (that's as specific as I can be right now), so if you can wait, you
might get what you're looking without any work at all. I expect that a
side effect of my effort would be better documentation for how class and
function loading works in the master, so it'd probably be of benefit
regardless.
Bill1
On Wed, 21 Jan 2009, Marcus Agehall (Roxen IS) @ Pike (-) importmöte för
mailinglistan wrote:
> When it comes to limiting the users, I think you will have to write
> your own master that prevents them from accessing modules that can be
> "dangerous".
>
> The current master used in Pike isn't excatly the easiest piece of
> code to look at, but it may give you ideas about what you need to do.
>
> There may also be other ways to accomplish this, but I don't know how
> this could be done.
|