Fix architecture diagram

zap-lib · Nov 18, 2023 · 4c55957 · 4c55957
1 parent a6cc37f
commit 4c55957
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/architectures/README.md b/src/architectures/README.md
@@ -2,7 +2,7 @@
 
 Zap is structured as a client-server model. The client unidirectionally sends data, and the server receives and processes it. This architecture keeps Zap's design simple and naturally allows a 1:N structure where multiple clients can send data to a single server.
 
-![](https://user-images.githubusercontent.com/6410412/283972762-95116c23-542e-40ed-b408-5ee1c00c86ea.png)
+![](https://user-images.githubusercontent.com/6410412/283973098-a0ffa51f-8db8-4f50-ac17-8e1ca914dd43.png)
 
 A data sent from the client to the server is transmitted over UDP socket. Zap is implemented to send this data by defining 'ZAPP Object' defined on top of datagram, which contain the client's UUID, resource type, and the actual data value. ZAPP Object is the data unit of ZAPP(Zap Protocol), for more detailed information about the protocol, please check the [ZAPP page](./zap-protocol.md).
 

diff --git a/src/introduction.md b/src/introduction.md
@@ -16,7 +16,7 @@ Of course, it can also become a simple remote controller, not a motion controlle
 
 To overcome the limitation that data sources are confined to a single mobile device, Zap provides its own network protocol and programming interface to access data sources on other devices. Please check the [Architectures](./architectures) section for more information about Zap's communication specification and structure.
 
-![](https://user-images.githubusercontent.com/6410412/283972762-95116c23-542e-40ed-b408-5ee1c00c86ea.png)
+![](https://user-images.githubusercontent.com/6410412/283973098-a0ffa51f-8db8-4f50-ac17-8e1ca914dd43.png)
 
 In the following application code blocks, it shows that the client instance on an Android device sends acceleration force data to the server device.