Internal Server Error: Missing headers or other script malfunction. Check the logs or contact cs-sysadmin@wellesley.edu
My apologies. There were some technical issues I ran into moving to
the new server that I haven't had time to fix, and this is yet another
of them. When/if you run into things like this, you can usually edit
the URL to access oldcs.wellesley.edu
instead
of cs.wellesley.edu
and it should work.
The processor (CPU) can access data in memory (RAM) in a few nanoseconds. To read data from disk takes a few milliseconds. So memory is a million times faster.
When your program starts, the code is read from disk into memory, and the processor runs the code from memory (moving data to the processor for computations).
disk is really only for long-term storage.
It's not a technical term. It's just an informal notion that things last and don't go away with the next request, page refresh, or whatever.
In the reading, we wanted the setting of whether the cart is shown or not to last until the user explictly sets to the other value. In other words, clicking "show cart" means that the cart will always be shown until the user clicks "hide cart".
Because we weren't using sessions. We were using plain old cookies. Flask's sessions use a digitally signed cookie, but all other cookies are normal.
Hmm. I think you may have mis-read that. We can create a session ID, but Flask doesn't. There is no difference between a session ID and a session identifier; ID == identifier.
If sessions are stored in files, then you are correct. PHP stores
its sessions in files (in /var/lib/php/sessions
). In
fact, that directory on Tempest currently has 571 files in it, some
dating back to September 4th. But they total less than half a
megabyte, so no big deal (yet).
Yes! Clearing browser cookies will probably mean you have to re-login to everything you've logged into.
Another technique that is sometimes used is to put a session id in
the
URL: https://domain.com/path/to/endpoint?sessid=29834792837492832
. You
then have to make the app append that session id onto every URL, so
that it's available in every request (like cookies).