Rename project to alpaca_websocket_proxy; static link openssl

Author: kzhdev

CMakeLists.txt

@@ -2,7 +2,7 @@ cmake_minimum_required(VERSION 3.15)
 
 file (STRINGS "version" BUILD_VERSION)
 
-project(websocket_proxy
+project(alpaca_websocket_proxy
         VERSION ${BUILD_VERSION}
         LANGUAGES CXX)
 
@@ -20,51 +20,54 @@ if (CMAKE_BUILD_TYPE MATCHES Release)
     add_definitions(-DNDEBUG)
 endif()
 
+set(VCPKG_TARGET_TRIPLET x64-windows-static)
+
 set(RELEASE_DIR "${CMAKE_CURRENT_BINARY_DIR}/release")
-file(COPY "${CMAKE_CURRENT_SOURCE_DIR}/include" DESTINATION "${RELEASE_DIR}")
-configure_file(src/version.h.in release/include/websocket_proxy/version.h)
+configure_file(src/version.h.in release/include/alpaca_websocket_proxy/version.h)
+
+set(OPENSSL_USE_STATIC_LIBS TRUE)
+set(OPENSSL_MSVC_STATIC_RT TRUE)
 
 find_package(boost_beast REQUIRED CONFIG)
 find_package(OpenSSL REQUIRED)
 find_package(spdlog REQUIRED CONFIG)
-
-set(OPENSSL_USE_STATIC_LIBS TRUE)
-set(OPENSSL_MSVC_STATIC_RT TRUE)
+add_definitions(-DSPDLOG_USE_STD_FORMAT -DSPDLOG_USE_STD_FORMAT_HO)
 
 include(cmake/slick_queue.cmake)
 
 set(HEADERS
-    include/websocket_proxy/type.h
-    include/websocket_proxy/websocket_proxy_client.h
+    include/alpaca_websocket_proxy/type.h
+    include/alpaca_websocket_proxy/alpaca_websocket_proxy_client.h
 )
 
 set(SOURCES
     src/main.cpp
-    src/websocket_proxy.cpp
+    src/alpaca_websocket_proxy.cpp
 )
 
-add_executable(websocket_proxy ${SOURCES})
-target_include_directories(websocket_proxy PUBLIC include ${slick_queue_SOURCE_DIR}/include ${spdlog_SOURCE_DIR} ${RELEASE_DIR}/include)
-target_link_libraries(websocket_proxy PRIVATE spdlog::spdlog Boost::asio Boost::beast OpenSSL::SSL OpenSSL::Crypto)
-target_precompile_headers(websocket_proxy PRIVATE src/pch.hpp)
+add_executable(alpaca_websocket_proxy ${SOURCES})
+target_include_directories(alpaca_websocket_proxy PUBLIC include ${slick_queue_SOURCE_DIR}/include ${spdlog_SOURCE_DIR} ${RELEASE_DIR}/include)
+target_link_libraries(alpaca_websocket_proxy PRIVATE spdlog::spdlog_header_only Boost::asio Boost::beast OpenSSL::SSL OpenSSL::Crypto)
+target_precompile_headers(alpaca_websocket_proxy PRIVATE src/pch.hpp)
 
 if (MSVC)
     add_definitions(-D_WIN32_WINNT=0x0A00)
     set(CMAKE_SUPPRESS_REGENERATION true)   # supress zero_check
-    set_target_properties(websocket_proxy PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}/bin")
-    set_target_properties(websocket_proxy PROPERTIES RUNTIME_OUTPUT_DIRECTORY_DEBUG "${CMAKE_BINARY_DIR}/bin/Debug")
-    set_target_properties(websocket_proxy PROPERTIES RUNTIME_OUTPUT_DIRECTORY_RELEASE "${CMAKE_BINARY_DIR}/bin/Release")
-    set_target_properties(websocket_proxy PROPERTIES LINK_INCREMENTAL ON)
-    target_compile_definitions(websocket_proxy PUBLIC _UNICODE) # set CharacterSet to unicode
-    target_compile_options(websocket_proxy PRIVATE "/bigobj")
-    set_target_properties(websocket_proxy PROPERTIES MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>")
+    set_target_properties(alpaca_websocket_proxy PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}/bin")
+    set_target_properties(alpaca_websocket_proxy PROPERTIES RUNTIME_OUTPUT_DIRECTORY_DEBUG "${CMAKE_BINARY_DIR}/bin/Debug")
+    set_target_properties(alpaca_websocket_proxy PROPERTIES RUNTIME_OUTPUT_DIRECTORY_RELEASE "${CMAKE_BINARY_DIR}/bin/Release")
+    set_target_properties(alpaca_websocket_proxy PROPERTIES LINK_INCREMENTAL ON)
+    target_compile_definitions(alpaca_websocket_proxy PUBLIC _UNICODE) # set CharacterSet to unicode
+    target_compile_options(alpaca_websocket_proxy PRIVATE "/bigobj")
+    set_target_properties(alpaca_websocket_proxy PROPERTIES MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>")
 endif()
 
 if (CMAKE_BUILD_TYPE MATCHES Release)
-    add_custom_command(TARGET websocket_proxy
+    add_custom_command(TARGET alpaca_websocket_proxy
         POST_BUILD
+        COMMAND ${CMAKE_COMMAND} -E copy_directory ${CMAKE_CURRENT_SOURCE_DIR}/include ${RELEASE_DIR}/include
         COMMAND ${CMAKE_COMMAND} -E copy_directory ${CMAKE_BINARY_DIR}/bin/Release ${RELEASE_DIR}/bin
-        COMMAND ${CMAKE_COMMAND} -E tar "cfv" "websocket_proxy_${BUILD_VERSION}.zip" --format=zip "${RELEASE_DIR}/bin" "${RELEASE_DIR}/include"
+        COMMAND ${CMAKE_COMMAND} -E tar "cfv" "alpca_websocket_proxy_${BUILD_VERSION}.zip" --format=zip "${RELEASE_DIR}/bin" "${RELEASE_DIR}/include"
         WORKING_DIRECTORY "${RELEASE_DIR}"
         COMMENT "Creating zip archive"
     )

README.md

@@ -1,15 +1,15 @@
-# WebsocketProxy: Share a Single WebSocket Connection for Multiple Clients (C++)
-WebSocketProxy provides a C++ WebSocket proxy framework that empowers you to share a single WebSocket connection among multiple clients, maximizing resource utilization and streamlining real-time data access.
+# AlpacaWebsocketProxy: Share a Single WebSocket Connection for Multiple Clients (C++)
+AlpacaWebSocketProxy provides a C++ WebSocket proxy framework that empowers you to share a single WebSocket connection among multiple clients, maximizing resource utilization and streamlining real-time data access.
 
 ## Built for Efficiency: Serving Multiple Clients with One Connection
-Designed initially for the [Alpaca.Market](https://alpaca.markets/), which offers data via both REST and WebSockets. However, Alpaca limits the number of concurrent WebSocket connections per account. WebSocketProxy solves this by enabling multiple strategies under the same account to receive real-tine market data updates through a single, shared WebSocket connection.
+Designed initially for the [Alpaca.Market](https://alpaca.markets/), which offers data via both REST and WebSockets. However, Alpaca limits the number of concurrent WebSocket connections per account. AlpacaWebSocketProxy solves this by enabling multiple strategies under the same account to receive real-tine market data updates through a single, shared WebSocket connection.
 
 ## Components and Communication
-WebSocketProxy consists of two components: 
+AlpacaWebSocketProxy consists of two components: 
 1. Standalone proxy server executable: This executable acts as the central communication hub. It manages the connection to the WebSocket server and handles data forwarding between clients. It's launched upon the first client attempting a WebSocket connection, ensuring only one server instance runs simultaneously. Any subsequent server launch attempts automatically terminate, preventing resource conflicts. The server continues execution until all connected clients are closed.
 2. Header-only Proxy Client: This lightweight client library integrates into your individual applications. It manages communication with the proxy server and provides a familiar interface for sending and receiving data.
 
-## Benefits of WebSocketProxy
+## Benefits of AlpacaWebSocketProxy
 * Efficient Resource Utilization: Share a single WebSocket connection, reducing overhead and improving resource management.
 * Real-Time Data Streamlining: Multiple trading strategies within an account gain access to crucial market updates concurrently.
 * Simplified Integration: The header-only client library enables effortless integration with your existing client applications.