Conventional and wireless ad hoc network

This infographic sample visualizes the Conventional and wireless ad hoc network. It was designed on the base of the Wikimedia Commons file: Běžná bezdrátová síť a ad hoc síť.png.
[commons.wikimedia.org/ wiki/ File:B%C4%9B%C5%BEn%C3%A1_ bezdr%C3%A1tov%C3%A1_ s%C3%AD%C5%A5_ a_ ad_ hoc_ s%C3%AD%C5%A5.png]
This file is licensed under the Creative Commons Attribution-Share Alike 4.0 International license. [creativecommons.org/ licenses/ by-sa/ 4.0/ deed.en]
"A wireless ad hoc network (WANET) is a decentralized type of wireless network. The network is ad hoc because it does not rely on a pre existing infrastructure, such as routers in wired networks or access points in managed (infrastructure) wireless networks. Instead, each node participates in routing by forwarding data for other nodes, so the determination of which nodes forward data is made dynamically on the basis of network connectivity. In addition to the classic routing, ad hoc networks can use flooding for forwarding data.
Wireless mobile ad hoc networks are self-configuring, dynamic networks in which nodes are free to move. Wireless networks lack the complexities of infrastructure setup and administration, enabling devices to create and join networks "on the fly" – anywhere, anytime." [Wireless ad hoc network. Wikipedia]
The infographic example "Conventional and wireless ad hoc network" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Computers and Communications solution from the Illustration area of ConceptDraw Solution Park.

"The client–server model of computing is a distributed application structure that partitions tasks or workloads between the providers of a resource or service, called servers, and service requesters, called clients. Often clients and servers communicate over a computer network on separate hardware, but both client and server may reside in the same system. A server host runs one or more server programs which share their resources with clients. A client does not share any of its resources, but requests a server's content or service function. Clients therefore initiate communication sessions with servers which await incoming requests.
Examples of computer applications that use the client–server model are Email, network printing, and the World Wide Web." [Client–server model. Wikipedia]
The UML communication diagram example "Client server access" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.