Confirmed users
574
edits
 (→Indexing:  Maybe dynamic markup generation is a priority-2 feature, since it enables permalinking. Does MXR really have that feature?)  | 
				|||
| Line 49: | Line 49: | ||
* (B) Index trees independently. A build failure in one (with an unchanged format version) shouldn't totally scuttle an instance update.  | * (B) Index trees independently. A build failure in one (with an unchanged format version) shouldn't totally scuttle an instance update.  | ||
* (B) Parallel and/or incremental indexing. This will let us scale to more trees.  | * (B) Parallel and/or incremental indexing. This will let us scale to more trees.  | ||
* (B) Dynamically generate markup, rather than building zillions of static files. This means we won't have to increment the format version nearly as often, so deployments won't block on time-consuming whole-instance rebuilds as often, so markup changes get into production faster. This might reduce the need for the above.  | * (B) (2?) Dynamically generate markup, rather than building zillions of static files. This means we won't have to increment the format version nearly as often, so deployments won't block on time-consuming whole-instance rebuilds as often, so markup changes get into production faster. This might reduce the need for the above. It will also enable us to think about serving up (unanalyzed but syntax-colored) older revisions of files, for [https://bugzilla.mozilla.org/show_bug.cgi?id=962108 permalinking].  | ||
* (3) Better support for JS, Python, etc.  | * (3) Better support for JS, Python, etc.  | ||
** Remove the C++ assumptions from the core so we can support structured queries on other languages. Python keeps coming up. Java and Scala did once as well. People mentioned JS a long time ago.  | ** Remove the C++ assumptions from the core so we can support structured queries on other languages. Python keeps coming up. Java and Scala did once as well. People mentioned JS a long time ago.  | ||