<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Localization in Model-Glue - Part I</title>
	<link>http://www.larcun.com/2008/04/17/localization-in-model-glue/</link>
	<description>The (time permitting) blog of Larkin Cunningham</description>
	<pubDate>Thu, 28 Aug 2008 04:51:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Free</title>
		<link>http://www.larcun.com/2008/04/17/localization-in-model-glue/#comment-5038</link>
		<dc:creator>Free</dc:creator>
		<pubDate>Fri, 25 Apr 2008 17:08:23 +0000</pubDate>
		<guid>http://www.larcun.com/2008/04/17/localization-in-model-glue/#comment-5038</guid>
		<description>I appreciate you cross-linking to my article, "Localization in Model-Glue 2".  But honestly - you missed something.  I mentioned at the bottom of my posting that localized text tokens are for another article.  The article provides a way to have localized views - and a fallback method when no localized view is present.  Combined with your approach - a full localization   internationalization system can easily be modeled.</description>
		<content:encoded><![CDATA[<p>I appreciate you cross-linking to my article, &#8220;Localization in Model-Glue 2&#8243;.  But honestly - you missed something.  I mentioned at the bottom of my posting that localized text tokens are for another article.  The article provides a way to have localized views - and a fallback method when no localized view is present.  Combined with your approach - a full localization   internationalization system can easily be modeled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Localization in Model-Glue - Part II at Clogging up the Web</title>
		<link>http://www.larcun.com/2008/04/17/localization-in-model-glue/#comment-4933</link>
		<dc:creator>Localization in Model-Glue - Part II at Clogging up the Web</dc:creator>
		<pubDate>Fri, 18 Apr 2008 19:37:45 +0000</pubDate>
		<guid>http://www.larcun.com/2008/04/17/localization-in-model-glue/#comment-4933</guid>
		<description>[...] My Photo Blog        &#171; Localization in Model-Glue [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] My Photo Blog        &laquo; Localization in Model-Glue [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larkin</title>
		<link>http://www.larcun.com/2008/04/17/localization-in-model-glue/#comment-4931</link>
		<dc:creator>Larkin</dc:creator>
		<pubDate>Fri, 18 Apr 2008 14:53:12 +0000</pubDate>
		<guid>http://www.larcun.com/2008/04/17/localization-in-model-glue/#comment-4931</guid>
		<description>I have implemented suggestion 1 above. Now I have a wrapper component for the resourceBundle component called resourceBundleCollection, which is now a structure containing the locale as a key to retrieve the resource bundle for the locale. I use coldspring to inject the directory path and a comma-delimited list of locales to load. Works a charm. Now I have just the locale string, e.g. "en_GB" stored in the session and I only retrieve the resource bundle each time in the request. This will have a lower memory footprint the more users there are.

I will post up the code solution for this soon. Most of what is above still holds true with the modifications I will post up.</description>
		<content:encoded><![CDATA[<p>I have implemented suggestion 1 above. Now I have a wrapper component for the resourceBundle component called resourceBundleCollection, which is now a structure containing the locale as a key to retrieve the resource bundle for the locale. I use coldspring to inject the directory path and a comma-delimited list of locales to load. Works a charm. Now I have just the locale string, e.g. &#8220;en_GB&#8221; stored in the session and I only retrieve the resource bundle each time in the request. This will have a lower memory footprint the more users there are.</p>
<p>I will post up the code solution for this soon. Most of what is above still holds true with the modifications I will post up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
