search

SteamedPears / CodeReviewClientMaster

Other
4 stars 3 forks source link

Stop using do/languages #23

Open spratt opened 12 years ago

spratt commented 12 years ago

Since we already have languages.json, we don't really need to have languages stored in the database. I'm thinking we should change the unique ids of the languages from numbers to their short-names such as "js" which are already stored in languages.json. This will reduce the number of ajax calls we need, and reduce the number of calls to the backend code, which should increase scalability.

spratt commented 12 years ago

Since this is mostly a backend thing, I'm assigning this to Christian.

Gankra commented 12 years ago

Could we just have do/languages link to langauges.json? I kind of like the uniformity/implementation-neutrality of do/languages as a URL.

spratt commented 12 years ago

That is probably doable, but I like putting as little strain on the backend as possible. The less the backend gets hit and the more we can use a cached static front end, the more requests we're going to be able to satisfy in some unit time.

Gankra commented 12 years ago

How much cost does a hardlink from do/languages to languages.json incur?

spratt commented 12 years ago

The back end is single threaded, so every request for a hard linked file would delay the processing of actual requests.