On Thu, Aug 14, 2003 at 09:51:28PM -0400, Edmund Lian wrote: > The problem then, is how to allow them to feel free to fiddle with > their customized bits, but also stop a fork of the common code.
Can you explore using a Content Management System to allow them to selectively import code specifict to their modules, but restrict them from importing the critical core modules? Along those lines, can you implement a $HOME/.application search path for "plugins"? Really, I understand that you feel a well-defined developer/user policy is not enough control for your situation. So be it. ;-) Ha! On one extreme, you could always use SOAP for controlling the core application API. Though, that's probably more work than just distributing byte code. *shrug* Well, I don't envy your situation. I hope it works out. -- Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/ assert(expired(knowledge)); /* core dump */
pgp00000.pgp
Description: PGP signature
