> The idea about letting the Mason parser produce separate files based on
> language may seem nice, but I wonder if the gain in computation is really
> that substantial. Especially when there are queries to remote DBs, reading
Yes, I know. However, making lots of hash lookups in runtime just
because we don't take the effort to implement translation earlier in the
chain, where it belongs to, now that's ugly. And since I'm just about
deciding what system to use, this question can be posed now. If I were
after the internationalization effort, I'd probably never do any steps
for a (much?) less then 1 percent saving.
> sessions, multiple components, etc. making the translation overhead a small
> part of the total cost, my gut feeling is that this is better handled with
> things like caching (Mason component caching) or network/browser caching
> (with all its pitfalls).
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 level of compiled mason components however, my suggestion of
localized .obj files trades some compile time and cache size for some
running speed, so in this meaning: yes, it can be handled with component
caching, which does not mead my suggestion doesn't have validity.
> Has anybody measured this once ? I guess not :-)
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
(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.)
If so, then I'll do some measurements...
Baldvin
-------------------------------------------------------------------------
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
