HTTP Session Token
A session token is a unique identifier that is generated and sent from a server to a client to identify the current interaction session. The client usually stores and sends the token as an HTTP cookie and/or sends it as a parameter in GET or POST queries. The reason to use session tokens is that the client only has to handle the identifier—all session data is stored on the server (usually in a database, to which the client does not have direct access) linked to that identifier. Examples of the names that some programming languages use when naming their HTTP cookie include JSESSIONID (JSP), PHPSESSID (PHP), and ASPSESSIONID (ASP).
Read more about this topic: Session (computer Science)
Famous quotes containing the words session and/or token:
“I need not tell you of the inadequacy of the American shipping marine on the Pacific Coast.... For this reason it seems to me that there is no subject to which Congress can better devote its attention in the coming session than the passage of a bill which shall encourage our merchant marine in such a way as to establish American lines directly between New York and the eastern ports and South American ports, and both our Pacific Coast ports and the Orient and the Philippines.”
—William Howard Taft (1857–1930)
“The token woman carries a bouquet of hothouse celery
and a stenographer’s pad; she will take
the minutes, perk the coffee, smile
like a plastic daisy and put out
the black cat of her sensuous anger
to howl on the fence all night.”
—Marge Piercy (b. 1936)