1. A program which provides some service to other ({client})
	programs.  The connection between client and server is
	normally by means of {message passing}, often over a
	{network}, and uses some {protocol} to encode the client's
	requests and the server's responses.  The server may run
	continuously (as a {daemon}), waiting for requests to arrive
	or it may be invoked by some higher level daemon which
	controls a number of specific servers ({inetd} on {Unix}).

	There are many servers associated with the {Internet}, such as
	those for {HTTP}, {Network File System}, {Network Information
	Service} (NIS), {Domain Name System} (DNS), {FTP}, {news},
	{finger}, {Network Time Protocol}.  On Unix, a long list can
	be found in /etc/services or in the {NIS} database "services".
	See {client-server}.

	2. A computer which provides some service for other computers
	connected to it via a network.  The most common example is a
	{file server} which has a local disk and services requests
	from remote clients to read and write files on that disk,
	often using {Sun}'s {Network File System} (NFS) {protocol} or
	{Novell Netware} on {PCs}.  Another common example is a {web
	server}.

	[{Jargon File}]

	(2003-12-29)

<World-Wide Web, database, tool> {Allaire Corporation}'s
	commercial {database} application development tool that allows
	{databases} to have a {World-Wide Web} {interface}, so a
	database can be queried and updated using a {web browser}.

	The ColdFusion Server application runs on the {web server} and
	has access to a {database}.  ColdFusion files on the web
	server are {HTML} pages with additional ColdFusion commands to
	{query} or {update} the database, written in {CFML}.  When the
	page is requested by the user, the {web server} passes the
	page to the Cold Fusion application, which executes the {CFML}
	commands, places the results of the {CFML} commands in the
	{HTML} file, and returns the page to the {web server}.  The
	page returned to the {web server} is now an ordinary {HTML}
	file, and it is sent to the user.

	Examples of ColdFusion applications include order entry, event
	registration, catalogue search, directories, calendars, and
	interactive training.  ColdFusion applications are robust
	because all database interactions are encapsulated in a single
	industrial-strength {CGI} script.  The formatting and
	presentation can be modified and revised at any time (as
	opposed to having to edit and recompile {source code}).

	ColdFusion Server can connect with any database that supports
	{ODBC} or {OLE DB} or one that has a native database driver.
	Native database drivers are available for {Oracle} and
	{Sybase} databases.

	ColdFusion is available for {Windows}, {Solaris}, and {HP-UX}.
	A {development environment} for creating ColdFusion files,
	called ColdFusion Studio, is also available for {Windows}.

	Current version: MX(6), as of 2003-07-11.

	The {filename extension} for ColdFusion files is .cfm

	{Home (http://www.coldfusion.com/)}.

	(2003-07-27)

<networking> /root/ The sequence of {hosts}, {routers},
	{bridges}, {gateways}, and other devices that network traffic
	takes, or could take, from its source to its destination.  As
	a verb, to determine the link down which to send a {packet},
	that will minimise its total journey time according to some
	{routeing algorithm}.

	You can find the route from your computer to another using the
	program {traceroute} on {Unix} or tracert on {Microsoft
	Windows}.

	(2001-05-26)

1. <language> {Synthesizer Specification Language}.

	2. <language> {Syntax/Semantic Language} (S/SL).

	3. <networking, World-Wide Web> {Secure Sockets Layer}.

	(1996-09-08)

<hardware> To press and release a {button} on a {mouse} or
	other {pointing device}.  This generates an {event}, also
	specifying the screen position, which is processed by the
	{window manager} or {application program}.  On a mouse with
	more than one button, the unqualified term usually implies
	pressing the left-most button (with the right index finger),
	other buttons would be qualified, e.g. "{right-click}".
	{Keyboard} modifiers may also be used, e.g. "shift-click",
	meaning to hold down the shift key on the keyboard while
	clicking the mouse button.

	If the mouse moves while the button is pressed then this is a
	{drag}.

	(1995-03-14)

1. <file system> {hard link} or {symbolic link}.

	2. <hypertext> {hyperlink}.

	(1997-10-22)

1. <hardware> A generic term for a {display device} that shows
	text and/or images on a roughly flat rectangular surface.  The
	most common type is usually refered to as a "{monitor}" and is
	based on a {cathode-ray tube}, though {flat panel} displays
	have, since around 2000, become increasingly competitive in
	price and performance.

	(2005-07-28)

	2. A {screen multiplexer} utility which lets you run multiple
	{interactive} {terminal sessions} (and {curses} programs)
	through a single terminal connection (on one {virtual
	console}, one terminal, through one {modem} link, {telnet}
	session or {xterm}).

	Screen can detach processes from one terminal and attach them
	to another.  "Auto-detach" lets you continue working after
	being disconnected and reconnected.  It supports keyboard
	driven cut and paste from any text and/or curses application
	(like {Lynx}) to any other (like {xemacs}).

	Screen comes with many {Linux} distributions and is available
	(free) on many other {Unix} {platforms}.

	(2005-07-29)

1. <World-Wide Web> {HTTP cookie}.

	2. <protocol> A handle, transaction ID, or other token of
	agreement between cooperating programs.  "I give him a packet,
	he gives me back a cookie".

	The ticket you get from a dry-cleaning shop is a perfect
	mundane example of a cookie; the only thing it's useful for is
	to relate a later transaction to this one (so you get the same
	clothes back).

	Compare {magic cookie}; see also {fortune cookie}.

	3. <security, jargon> A {cracker} term for the {password} list
	on a {multi-user} computer.

	4. <jargon> An adjective describing a computer that just
	became {toast}.

	(1997-04-14)

<networking> 1. A lasting connection between a user (or user
	agent) and a {peer}, typically a {server}, usually involving
	the exchange of many packets between the user's computer and
	the server.  A session is typically implemented as a layer in
	a network {protocol} (e.g. {telnet}, {FTP}).

	In the case of protocols where there is no concept of a
	session layer (e.g. {UDP}) or where sessions at the {session
	layer} are generally very short-lived (e.g. {HTTP}), {virtual}
	sessions are implemented by having each exchange between the
	user and the remote host include some form of {cookie} which
	stores state (e.g. a unique session ID, information about the
	user's preferences or authorisation level, etc.).

	See also {login}.

	2. A lasting connection using the {session layer} of a
	networking protocol.

	(1997-08-03)