Lines Matching refs:abstract
10 "abstract protocols" and "abstract transports".
12 
15 chunks of code hidden behind "ops" structs... the "abstract protocol"
19 The "abstract transport" implementation is responsible for sending
23 In the system, both the abstract protocols and transports are
34 any network. The abstract protocol itself has no relationship
47 The public api for defining abstract protocols and transports is
50 …- [abstract.h](https://libwebsockets.org/git/libwebsockets/tree/include/libwebsockets/abstract/abs…
51 …- [protocols.h](https://libwebsockets.org/git/libwebsockets/tree/include/libwebsockets/abstract/pr…
52 …- [transports.h](https://libwebsockets.org/git/libwebsockets/tree/include/libwebsockets/abstract/t…
90 through the abstract transport.
111 The abstract protocol has no idea about a network or network addresses
131 ## Steps for adding new abstract protocols
133 - add the public header in `./include/libwebsockets/abstract/protocols/`
134 - add a directory under `./lib/abstract/protocols/`
138 - search for "using any abstract protocol" and add your `LWS_WITH_xxx` to
142 `./lib/abstract/abstract.c`
144 ## Steps for adding new abstract transports
146 - add the public header in `./include/libwebsockets/abstract/transports/`
147 - add your transport sources under `./lib/abstract/transports/`
154 `./lib/abstract/abstract.c`
160 lws features an abstract transport designed to facilitate unit testing. This