9:55 AM
@AidenChow Imagine a person named Bob. Bob wants to run Funky code but the only way to do so is to send the program to a central processing factory via mail. Bob writes his program onto a piece of paper and sends it to the address of the Funky factory. The Funky factory gets Bob's code and executes it and generates results.
However, the workers at the Funky factory have no clue where to send the results to because all the incoming mail doesn't have a return address. Instead, they require people sending in code to also send a unique code that they give out to users who register at the Funky factory
So Bob goes and registers at the Funky factory. They ask for his address and in return give him a unique code that correlates to his name and address
Now, when Bob sends code to the Funky factory, he includes the program and his unique code that is linked to his address
The Funky factory processes the code and now, using the unique identifier, knows where to send the results to, and Bob gets his output
That's basically how the session cookie works in this instance if I've understood what ATaco is saying correctly
The only information the session cookie has is a string of random characters (such as iwOkJWK82nkiwnwKWNO
) which it associates with your computer (most likely your IP)