| Did you know ... | Search Documentation: |
| Pack logtalk -- logtalk-3.101.0/docs/apis/_sources/http_websocket_client_service_0.rst.txt |
.. index:: single: http_websocket_client_service .. _http_websocket_client_service/0:
.. rst-class:: right
object
http_websocket_client_service
By default, the client-side convenience for callback-driven WebSocket sessions with atom text representation, combining the opening handshake, optional initial outbound messages, and the higher-level session loop, uses the http_socket_transport library.
| Availability:
| logtalk_load(http_websocket_service(loader))
| Author: Paulo Moura | Version: 1:0:0 | Date: 2026-07-09
| Compilation flags:
| static, context_switching_calls
| Extends:
| public :ref:`http_websocket_service(http_socket_transport,client,atom) <http_websocket_service/3>`
| Remarks: | (none)
| Inherited public predicates: | Â :ref:`http_websocket_session/2::initial_state/1` Â :ref:`http_websocket_messages/1::is_message/1` Â :ref:`http_websocket_session/2::is_state/1` Â :ref:`http_websocket_messages/1::message/3` Â :ref:`http_websocket_messages/1::payload/2` Â :ref:`http_websocket_messages/1::read_message/2` Â :ref:`http_websocket_session/2::read_message/4` Â :ref:`http_websocket_session/2::read_message/5` Â :ref:`http_websocket_session/2::read_message/6` Â :ref:`http_websocket_service/3::run_session/3` Â :ref:`http_websocket_service/3::run_session/4` Â :ref:`http_websocket_messages/1::type/2` Â :ref:`http_websocket_session/2::write_message/2` Â :ref:`http_websocket_session/2::write_message/3` Â :ref:`http_websocket_session/2::write_message/4` Â :ref:`http_websocket_session/2::write_message/5` Â
.. contents:: :local: :backlinks: top
(no local declarations; see entity ancestors if any)
(no local declarations; see entity ancestors if any)
(no local declarations; see entity ancestors if any)
(none)