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

I think this is probably the right thing to do. While we can technically make almost anything configurable down to the last button and knob, it's usually better to pick a reasonable level to stop. You aren't usually going to have some sections in one encoding and some in another, and if you have different languages UTF-8 will cover you. Of course, I've never used anything like Shift-JIS which won't work with UTF-8....

> 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?
> 
> discussed in CACHE-38 and CACHE-159
> 
> Message was edited by: 
>         dres

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