Caching different http-requests
$begingroup$
There have been multiple discussions on caching http-requests with RXJS. In this question/proposal I want to propose a custom rxjs-operator (non-pure) to provide caching:
const cacheHttp = (cacheKey: string, cacheStorage: any) => (source: Observable<any>) => {
if (!cacheStorage[cacheKey]) {
cacheStorage[cacheKey] = source.pipe(
shareReplay(1)
);
}
return cacheStorage[cacheKey];
};
This operator is not pure, as it modifies one of its arguments (cacheStorage).
This operator could be used like this:
public cachedItems = {};
public getDataForItem$(itemId: string) {
return this.http.get('/item/' + itemId).pipe(
cacheHttp(itemId, this.cachedItems),
shareReplay(1)
);
}
The client could then call this multiple times without causing superfluous http-requests:
// the following two subscriptions cause http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// all further subscriptions would not cause any additional http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// this subscription would again cause an http-request:
this.itemService.getDataForItem('thirdItem').subscribe((val) => console.log(val));
Is this an acceptable approach to solving the "cache-for-different-requests-problem"? Is there possibly a memory-leak or are there any leaked subscriptions? Is it ok to have side-effects on a provided argument?
javascript cache angular-2+ rxjs
edited 20 mins ago
Jamal♦
30.3k11119227
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
$endgroup$
add a comment |
$begingroup$
There have been multiple discussions on caching http-requests with RXJS. In this question/proposal I want to propose a custom rxjs-operator (non-pure) to provide caching:
const cacheHttp = (cacheKey: string, cacheStorage: any) => (source: Observable<any>) => {
if (!cacheStorage[cacheKey]) {
cacheStorage[cacheKey] = source.pipe(
shareReplay(1)
);
}
return cacheStorage[cacheKey];
};
This operator is not pure, as it modifies one of its arguments (cacheStorage).
This operator could be used like this:
public cachedItems = {};
public getDataForItem$(itemId: string) {
return this.http.get('/item/' + itemId).pipe(
cacheHttp(itemId, this.cachedItems),
shareReplay(1)
);
}
The client could then call this multiple times without causing superfluous http-requests:
// the following two subscriptions cause http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// all further subscriptions would not cause any additional http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// this subscription would again cause an http-request:
this.itemService.getDataForItem('thirdItem').subscribe((val) => console.log(val));
Is this an acceptable approach to solving the "cache-for-different-requests-problem"? Is there possibly a memory-leak or are there any leaked subscriptions? Is it ok to have side-effects on a provided argument?
javascript cache angular-2+ rxjs
edited 20 mins ago
Jamal♦
30.3k11119227
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
$endgroup$
add a comment |
$begingroup$
There have been multiple discussions on caching http-requests with RXJS. In this question/proposal I want to propose a custom rxjs-operator (non-pure) to provide caching:
const cacheHttp = (cacheKey: string, cacheStorage: any) => (source: Observable<any>) => {
if (!cacheStorage[cacheKey]) {
cacheStorage[cacheKey] = source.pipe(
shareReplay(1)
);
}
return cacheStorage[cacheKey];
};
This operator is not pure, as it modifies one of its arguments (cacheStorage).
This operator could be used like this:
public cachedItems = {};
public getDataForItem$(itemId: string) {
return this.http.get('/item/' + itemId).pipe(
cacheHttp(itemId, this.cachedItems),
shareReplay(1)
);
}
The client could then call this multiple times without causing superfluous http-requests:
// the following two subscriptions cause http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// all further subscriptions would not cause any additional http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// this subscription would again cause an http-request:
this.itemService.getDataForItem('thirdItem').subscribe((val) => console.log(val));
Is this an acceptable approach to solving the "cache-for-different-requests-problem"? Is there possibly a memory-leak or are there any leaked subscriptions? Is it ok to have side-effects on a provided argument?
javascript cache angular-2+ rxjs
edited 20 mins ago
Jamal♦
30.3k11119227
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
$endgroup$
There have been multiple discussions on caching http-requests with RXJS. In this question/proposal I want to propose a custom rxjs-operator (non-pure) to provide caching:
const cacheHttp = (cacheKey: string, cacheStorage: any) => (source: Observable<any>) => {
if (!cacheStorage[cacheKey]) {
cacheStorage[cacheKey] = source.pipe(
shareReplay(1)
);
}
return cacheStorage[cacheKey];
};
This operator is not pure, as it modifies one of its arguments (cacheStorage).
This operator could be used like this:
public cachedItems = {};
public getDataForItem$(itemId: string) {
return this.http.get('/item/' + itemId).pipe(
cacheHttp(itemId, this.cachedItems),
shareReplay(1)
);
}
The client could then call this multiple times without causing superfluous http-requests:
// the following two subscriptions cause http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// all further subscriptions would not cause any additional http-requests
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('firstItem').subscribe((val) => console.log(val));
this.itemService.getDataForItem('secondItem').subscribe((val) => console.log(val));
// this subscription would again cause an http-request:
this.itemService.getDataForItem('thirdItem').subscribe((val) => console.log(val));
Is this an acceptable approach to solving the "cache-for-different-requests-problem"? Is there possibly a memory-leak or are there any leaked subscriptions? Is it ok to have side-effects on a provided argument?
javascript cache angular-2+ rxjs
javascript cache angular-2+ rxjs
edited 20 mins ago
Jamal♦
30.3k11119227
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
edited 20 mins ago
Jamal♦
30.3k11119227
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
edited 20 mins ago
Jamal♦
30.3k11119227
edited 20 mins ago
Jamal♦
30.3k11119227
edited 20 mins ago
Jamal♦
30.3k11119227
30.3k11119227
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
asked Feb 4 at 15:51
Tobias GassmannTobias Gassmann
1061
1061
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
});
});
}, "mathjax-editing");
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "196"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f212854%2fcaching-different-http-requests%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Code Review Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f212854%2fcaching-different-http-requests%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
