From e042129eddeb06c9272a6544c67f9222c347ab10 Mon Sep 17 00:00:00 2001 From: xengineering Date: Fri, 21 Mar 2025 22:33:41 +0100 Subject: fw: ws: Add WebSocket interface The primary interface for this firmware was so far HTTP. This protocol is not suitable for small and bidirectional messages which are time-critical. If something like this needs to be implemented with HTTP the best approach is likely long-polling which at least makes it possible for the server / the firmware to send data to the client / user as reaction to an event like a closed door sensor. TCP would fix this issue and is a good choice. Nevertheless web clients are not allowed to open TCP connections for security purposes. Thus the WebSocket protocol was created to fill this gap. To not duplicate the any effort the WebSocket API should be used for small, time-critical messages for all clients (one with TCP support like CLI tools as well as web clients). HTTP is still kept to provide a web page but also for functionality where HTTP is more suitable like firmware uploads. --- fw/CMakeLists.txt | 1 + 1 file changed, 1 insertion(+) (limited to 'fw/CMakeLists.txt') diff --git a/fw/CMakeLists.txt b/fw/CMakeLists.txt index c0b9484..5aaf319 100644 --- a/fw/CMakeLists.txt +++ b/fw/CMakeLists.txt @@ -24,6 +24,7 @@ target_sources(app "${CMAKE_CURRENT_SOURCE_DIR}/src/syslog.c" "${CMAKE_CURRENT_SOURCE_DIR}/src/mac.c" "${CMAKE_CURRENT_SOURCE_DIR}/src/http.c" + "${CMAKE_CURRENT_SOURCE_DIR}/src/ws.c" "${CMAKE_CURRENT_SOURCE_DIR}/src/heart.c" ) -- cgit v1.2.3-70-g09d2