Hi.
Imagine a simple route like this:
app.get('/test',
apiCall1(),
apiCall2(),
apiCall3(),
apiCall4(),
apiCall5(),
renderPage()
How would you prevent this code from being executed by the same client
while said client is spamming GET requests (either by refresh page or
clicking buttons, etc.) to the same route ?
I'm using express (+session, static, bodyparser) and have failed to figure
this out on my own.
For example when I first visit /test in the browser, it works fine. But if
I then quickly refresh the page twice in a row, I get to the route twice
for the same session, which in turn doubles the amount of API calls from 5
to 10.
I want it to only occur once, and render the page. I've tried session
variables like "isRequesting true/false" and such, but nothing works,
because the response object changes upon a new request, meaning renderPage
cant use res.send on the "latest" response object.
Cheers.
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/cf81af35-399e-4842-8d9d-d8095d54f3bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
