Sure. The word "server" is used in lots of ways, because lots of things provide services.
A website is a collection of web pages sitting on a web server. E.g. www.wellesley.edu
You use res.body
when the request was sent from a FORM METHOD=POST
you use res.query
when the request was sent from a FORM METHOD=GET
Both! They are sent back and forth between browser and server with each request.
In practice, the browser often does nothing with them except send them back to the server, so they are often used for the backend to communicate with itself.
The best metaphor is a "claim check".
That gets us a little outside the course into the field of cryptography, but let's give it a try:
Instead:
Charlie doesn't have Bob's secret key, and so he can't fake E(M).
This also means that if Charlie intercepts the message from Bob to Alice, he can't substitute N. He can't (successfully) tamper with M in any way.
In the scenario above, Charlie would be attempting to tamper with the cookie in the browser or in transit between browser and server.
It is rendering, but it's rendering from a store of messages. The server can easily put a message in the list of messages, and the renderer automatically (well, because we put the code in there) renders everything in the list of messages.
For sure.
Sorry about the link. I'll fix that over the break.
No questions yet (not in like a I completely understand it kind of way, but like I need the info to marinate in my brain kind of way), I think just going through it in class would be nice!
I hope you have a sunny and restful break!
Thanks!