الجلسات مقابل الرموز (Tokens)

في هذا الدرس

compare the two common ways to stay logged in.

الموضوعات المخطط لها

• Session: after login the server stores state and gives the client a session ID, usually in a cookie. Each request sends it back.
• Token: after login the server gives a signed token (for example a JWT) that the client sends in Authorization: Bearer .... The server verifies it without stored state.
• Sessions are simple to revoke but need shared storage when you run several instances.
• Tokens scale easily across instances but are harder to revoke before they expire.
• Browser apps often use cookie sessions; mobile apps and APIs often use tokens. JNR-P5 implements them.