Hi, On Tue, Oct 1, 2013 at 4:35 PM, Slavik Goltser <[email protected]> wrote:
> That is a good point. I tried to be as close as possible to the original. > Mason and HTML::Mason are totally different beasts internally. I don't think you should have this as a goal. Your goal should be to make the best Template plugin for Mason users. What are you thoughts on data_dir? I would like to stick with how the > original plugin implemented it (as a dir next to views/). One other reason > for that is (according to the doc) is that you win a bit on startup as you > don't have to recompile the module, although I kind of feel like startup > time is a bit of a moot point for an application that technically does not > get restarted often. > I rather have the Mason default myself. The Mason documentation already mention that you should define a data_dir to a directory somewhere if you care about performance that much. I can say that defaulting to views/data will not work on my apps, that part of the tree is not writable by the user that runs the webapp. For most common use, having a fresh data_dir on restart is actually a good thing, it makes debugging situations with timestamps between deployed .mc/.mi files and cached compiled objects simpler.. So I still prefer my way: kill it, let users override all config. Bye, -- Pedro Melo @pedromelo http://www.simplicidade.org/ xmpp:[email protected] mailto:[email protected]
_______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
