Putting core classes above the web root - good or bad idea?
<p>We are developing several web applications to run on our own server that will share a number of core classes as part of their MVC setup.</p>

<p>I'm thinking of putting the classes above the web root so all applications can autoload() those classes using just one copy and not worry about synching issues.</p>

<p>Specialised classes would go in their relevant web directory, but shared libraries would go under /var/www/shared-libraries or something similar.</p>

<p>Apart from the potential to crash all sites simultaneously with a bad line of code, is there any reason why I wouldn't want to go down this path?</p>

<p>Thanks.</p>
