[Opensymphony-oscache] 2.1.1 delayed until I fix the encoding issue

This is actually a simple problem but it takes some understanding of what the users want.  In my opinion the character encoding (ie. UTF-8, etc...) should be set globally for the application and not overriden per page.  THis can be done using oscache.properties or a system property such as, file.encoding.  All other libraries I have used resolve this issue in this way.  

The alternative (while more flexible but much slower) is to use the headers to dynamically encode cached content on output.  So we can store it encoded in one charset and present it to the user in any acceptable one.  I don't think this makes sense.

If you are creating an i18n site then you know you will have to support UTF-8, so just bit the bullet and encode all output in that charset.  All modern browsers will support it and if they don't have the right language pack installed, so be it.

Opinions anyone?

---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=1512&messageID=4630#4630