1  |   Order by index

Jan 1, 2004, 12:05pm

This is a standard HTTP 1.1 header. Please support it.

Jan 1, 2004, 5:21pm

For what reason?....

- MR
[View Quote]

Jan 1, 2004, 6:28pm

[View Quote] So users don't accidently waste 10 seconds of their time clicking a
world with people in it and not have it be in their native language...
of course.

--
--Bowen--
http://bowen.homelinux.com
Give me ideajuice.

Jan 1, 2004, 6:41pm

Generally for the purpose which it's intended... to deliver appropriate
content to the requester based on their lanugage preference.

Even with the built in web browser, the users language preference
is transmitted with GET requests via the Accept-Language header,
just as it should be.

The 3D browser however does not provide an Accept-Language
header with it's GET requests.

I feel that it would be very appropriate for it to do so.

AWI obviously feels strong enough about the international market
to allow for the buttons and menus and help files to be swapped
out with versions covering other languages according to a choice
the user makes in their settings.

The users settings should extend to the OP path so that the content
can also be sensitive to their choice.

[View Quote]

Jan 1, 2004, 6:45pm

Erm.. but they have to be in the world to get the objects....

- MR

[View Quote]

Jan 1, 2004, 6:49pm

You have to consider you would need to actually set this inside the browser,
if only for testing purposes, if you end up having to cache every single
version in every single language you provided, simply to make sure its
right, and the AW browser has no capability for caching files of the same
name, but different language responses. It goes a lot deeper than just 'put
it in the ruddy string'

- MR

[View Quote]

Jan 1, 2004, 8:13pm

It's really dead simple. It's not 'deep' at all.

"stuff" comes from "op path"
"user" has "preferences"
"stuff" depends on "preferences"

Now put your mind to work figuring out how "op path" delivers
correct "stuff" according to "preferences"

The answer?

'put it in the ruddy string'

Now.. you can look deeper if you want to, but you will waste a whole
lot of time coming to the same conclusions....

The OP path needs to know what the preferences are, or it can never
deliver dynamic content according to the users preferences.

The user selects their language and rating preferences inside the browser.

Therefore, the browser should transmit this information to the op path
server with each request.

[View Quote]

Jan 1, 2004, 8:37pm

[View Quote] Web browsers seem to manage it just fine. I don't see a reason why anyone would
bother caching every language. The browser could keep one file cached that is of
the language you provide to the server. Very simple.

--
-Agent1

1  |   Order by index