-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
support content-negotiation for languages (issue #32)
- Loading branch information
Showing
1 changed file
with
6 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
143f118
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bibdia's current OPAC, which contains the user functions which this specification is trying to standardize, allows the user to select his language from the start. Living in France using a German browser I never get the language that I require - English - because everybody keeps second guessing me.
What I dislike about this specification is it's inconsistancy. Parameters - that is information which the user is sending to the server in order to perform a function - are inconsistantly encoded. Partly in the URL, partly as conventional parameters (after ? in the URL or as xxx-urlencoded POST or a JSON) and also hidden from view in HTTP headers - Accept-Language and Bearer Tokens for example. I'd put all these parameters in a conventional GET/POST request returning JSON data. An AngularJS service to support this would be quite simple to write.