"Caching" of Topic Page Parsing

[cycomachead]

From @cycomachead on March 25, 2014 11:50

This probably goes in the with LLAB changes, but it would be smart to save the parsed version of a topic file. I'm not sure of the best way to do this, perhaps a JSON object in local storage?

We could have a JSON object per lab/topic and then access that to build the topic page and to build the drop down. That would speed things up a lot, hopefully. :)

This is what I think we could do: SESSION START:

• Check if old topic object exists
  • if so, can it.
• Check if current topic object exists:
  • if so, use it.
• If not:
  • Use bjc-topic to create a parsed JSON object.
• Save the JSON to local storage
• Use that to build the topic page / drop down menu.

Copied from original issue: beautyjoy/bjc-r#272

[cycomachead]

Instead of local Storage, we can use session Storage. This would solve caching issues.

[xtitter]

a build system would fix this...