Shibboleth Developers

[Chad La Joie <>]

I think having the JSON producer do this makes the most sense.  As you
mentioned, you can't get access to the language preferences via
Javascript, but the JSON producer will see them when the request comes
in.  In most cases this is a list and so the producer could do
intelligent things like filter out all but the most preferred in any
given choice which is really what you'd want it to do.

On Wed, Jun 15, 2011 at 03:50, Rod Widdowson 
<>
 wrote:
> Those of you who have spoken to me for more than, say 5 seconds, about the 
> EDS and javascript will have heard my rant about how
> crappy the environment is because it doesn't allow access to the browsers 
> preferred languages setting, only the installed languages
> (via various non standard hooks).
>
> I was just watching an interesting discussion in JIRA about metadata 
> filtering for the EDS (the answer is that it should be done in
> the SP because the SP needs to be doing it anyway) and that provoked a 
> though:  Longer term, should we be getting the server which
> provides the DS feed to do this filtering for us? That is to say rather 
> than just sending down the JSON-ized <mdui:UIInfo/>
> statements, we actually look at the header, extract the language and do 
> something sensible with the content?
>
> Rod
>
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered