Skip to content

Update Memory Cache.js #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Memory Cache.js #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions src/misc/JavaScript/Memory Cache.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,11 +20,9 @@ function wrapLoop(fn) {
// there are two ways of saving Memory with different advantages and disadvantages
// 1. RawMemory.set(JSON.stringify(Memory));
// + ability to use custom serialization method
// - you have to pay for serialization
// - unable to edit Memory via Memory watcher or console
// 2. RawMemory._parsed = Memory;
// - undocumented functionality, could get removed at any time
// + the server will take care of serialization, it doesn't cost any CPU on your site
// + maintain full functionality including Memory watcher and console

// this implementation uses the official way of saving Memory
Expand Down