Yeah! That's my point!

Still, putting it in own namespace doesn't matter much, you could still be able to access other namespaces, right? So it still isn't shared hosting safe.

Alto when I think about it, it wont be able to mess with anything else's, than what is already yours.

If mod_perl2 is usable for shared hostings, than great! But is it suitable for them considering other things (memory usage for instance)?

Still mod_perl requires from you to be a good programmer, and even if it would be shared hosting safe, it wouldn't be for the "masses".

Alto that way, we (we - as somewhat good programmers :) could write applications for a mass usage on shared hosting - which would be better than where we are now.

And "masses" couldn't brake anything even if they try writing some bad code, right?

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.