Клиент–сервер моделі: Нұсқалар арасындағы айырмашылық
Content deleted Content added
ш Bot: Migrating 37 interwiki links, now provided by Wikidata on d:q146813 (translate me) |
ш clean up, replaced: июня → маусым using AWB |
||
1-жол:
[[File:Two-tier architecture.ru.svg|thumb|right|200px|Екі деңгейлі архитектура мысалы.]]
'''
<!--
11-жол:
''Functions'' such as email exchange, web access and database access are built on the client/server model. Users accessing banking services from their computer use a web browser client to send a request to a web server at a bank. That web server runs a program which may in turn, forward the request to its own database client program, which sends a request to the bank's database server (which runs on another computer) to retrieve the account information. The balance and transaction records are returned to the bank database client, which in turn serves it back to the user's web browser client, displaying the results to the user.
The client–server model has become one of the central ideas of [[network computing]]. Many business applications being written today use the client–server model, as do the Internet's main application protocols, such as [[HTTP]], [[SMTP]], [[Telnet]], and [[Domain Name System|DNS]].
The interaction between client and server is often described using [[sequence diagram]]s. The [[Unified Modeling Language]] has support for sequence diagrams.
18-жол:
Specific types of servers include [[web server]]s, [[ftp server]]s, [[application server]]s, [[database server]]s, [[name server]]s, [[mail server]]s, [[file server]]s, [[print server]]s, and [[terminal server]]s. Most [[web service]]s are also types of servers.
вычислительная или сетевая архитектура, в которой задания или сетевая нагрузка распределены между поставщиками услуг (сервисов), называемыми серверами, и заказчиками услуг, называемыми клиентами. Нередко клиенты и серверы взаимодействуют через компьютерную сеть и могут быть как различными физическими устройствами, так и [[Программное обеспечение | программным обеспечением]].
Line 43 ⟶ 42:
'''Сеть с выделенным сервером''' ({{lang-en|Client/Server network}}) — это [[локальная вычислительная сеть|локальная вычислительная сеть (LAN)]], в которой сетевые устройства централизованы и управляются одним или несколькими серверами. Индивидуальные рабочие станции или клиенты (такие, как ПК) должны обращаться к ресурсам сети через сервер(ы).
==Comparison to peer-to-peer architecture==
Line 53 ⟶ 51:
In the peer to peer network, software applications can be installed on the single computer and shared by every computer in the network. They are also cheaper to set up because most desktop operating systems have the software required for the network installed by default. On the other hand, the client/server model works with any size or physical layout of LAN and doesn't tend to slow down with a heavy use.<ref>[Peer-to-Peer Networking and Applications]</ref>
Peer-to-peer networks are typically less secure than client/server networks because security is handled by the individual computers, not controlled and supervised on the network as a whole. The resources of the computers in the network can become congested as they have to support not only the workstation user, but also the requests from network users. It may be difficult to provide systemwide services when the client operating system typically used in this type of network is incapable of hosting the service.
Client/server networks with their additional capacities have a higher initial setup cost for networking than peer to peer networks. The long-term aspect of administering a client/server network with applications largely server-hosted surely saves administering effort compared to administering the application settings per each client. In addition the concentration of functions in performant servers allows for lower grade performance qualification of the clients.
It is possible to set up a server on a modern desktop computer, but it is recommended to consider investment in enterprise-wide server facilities with standardised choice of hardware and software and with a systematic and remotely operable administering strategy. It is easier to configure and manage the server hardware and software compared to the distributed administering requirements with a flock of computers.<ref>Book: Computers are your future</ref><ref>Peer to Peer vs. Client/Server Networks</ref>
Line 65 ⟶ 63:
| author = Валерий Коржов
| authorlink =
| datepublished = 17
| url = http://www.osp.ru/nets/1997/06/142618/
| title = Многоуровневые системы клиент-сервер
Line 85 ⟶ 83:
[[Санат:Компьютер желілері архитектурасы]]
[[
| |||