one hurdle i have found to using catalyst's myapp_server.pl has been the headaches of it (typically) running under the user's permissions, and apache running under its own permissions, and the resulting permission conflicts in the mason data/obj directories when you move from one to the other.
i am sure it is solvable (the HTML::Mason::Interp instantiator could tell mason not to use obj files when running under myapp_server, myapp_server could be suid, or..?) the other hurdle is having to reinvent any Alias, LocationMatch, and Rewrite rules that apache is typically handling (ie, /static/foo.gif or /otherapp/drawgraph.cgi). i haven't thought of a good solution other than allocating every developer multiple ports, and adding even more complexity to the url/link generating code to know which port to use for which feature depending on which development environment.. > Mark - it definitely is not just you. Module reloading is frustrating > precisely because it works much of the time but not all of the time. > This is just the nature of Perl modules - they can do too many funky > things that depend on compilation order or on things that can only > reliably run once per process. > > I do encourage you to check out Catalyst and the auto-restarting > server. I was skeptical of this at first, but if you've got a > reasonably fast machine, then it works well. By the time you hit > "save" in your editor and move over to your browser to reload, > Catalyst has generally finished restarting. > > Jon ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
