On Tuesday 09 January 2007 15:41, Kovacs Baldvin wrote: > Considering that result pages of a webapp are almost never cacheable, I > don't see any way to introduce caching to the problem of translation.
On the page level, I totally agree. But typically, the page is built from independent (mason) components, and those can be cached by Mason with the key being the language tag. That's what I had in mind, but don't know how practical this wold be... What comes out of a DB cannot be easily translated I reckon... > Hey, at least I found something I can be first in :-). I think I'll > look into the solution that Ben told about, I hope he gives some code. > I'll check it out if it is similar than the localized .obj files idea I think that may be nice as well. A language=>compiler hash :-) However, I don't seem to have received Ben's email, so that is a conjecture... > (He talks about separate compilers for locales, I didn't think that, > I was thinking about tweaking the compiler itself. However, maybe his > solution is even better.) It's because it's outside of Mason, where it's called 'developing' and not 'hacking' :-) --paf -- --paf ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
