Find out
A client/server architecture can be defined as a network architecture in which the client (user interface, e.g. a computer) is separated from the application server. The client connects to a central server and sends the requests which are then processed. More precisely, the client offers the user interface for the application, while the server provides the data or resources and the functionality. The client-server architecture can consist of one server and a single computer or of a whole computer network.
Example
An example of client-server architecture is the WWW. If somebody is reading a newspaper online from a computer, this computer and its browser will function as client, while the computers, databases and software that host the newspaper constitute the server. A request for a web page with a particular newspaper article is sent from the computer to the server.
As soon as the server finds the information requested, it sends the page back to the computer, where it will be displayed by the browser.
Why is this information important for translators and translation teachers?
With the increasing globalisation of localisation markets and the optimisation of work processes, software development in the field of translation and localisation is tending towards client/server architectures. Some examples are workflow management tools – such as Plunet Business Manager, workflow management components in across, Trados Teamworks, as well as translation tools (e.g. Trados MultiTerm Server, TM Server, MultiTerm Anywhere, etc.).