Lines Matching full:application

19 The server operation is generally transparent for the application, running in a
20 background thread. The application can control the server activity with
24 application callbacks, allowing the server to interact with the application (for
32 * Dynamic resources - content provided at runtime by respective application
46 the application.
57 The linker section for services is predefined locally, however the application
72 Finally, the linker file and linker section have to be added to your application
94 The application needs to define an HTTP service (or multiple services), with
133 Application can enable resource wildcard support by enabling
156 in the application:
177 The resource content and content encoding is application specific. For the above
179 following code to the application's ``CMakeLists.txt`` file:
194 example shows how the path can be defined as a static resource in the application:
220     HTTP_SERVER_CONTENT_TYPE(json, "application/json")
226 the server and the application.
284 the application should be able to keep track of the received data progress.
286 The ``status`` field informs the application about the progress in passing
287 request payload from the server to the application. As long as the status
288 reports :c:enumerator:`HTTP_SERVER_DATA_MORE`, the application should expect
290 Once all request payload has been passed to the application, the server reports
295 the application shall reset any progress recorded for the resource, and await
299 The ``request_ctx`` parameter is used to pass request data to the application:
301 * The ``data`` and ``data_len`` fields pass request data to the application.
304   headers to the application, if
307 The ``response_ctx`` field is used by the application to pass response data to
310 * The ``status`` field allows the application to send an HTTP response code. If
313 * The ``headers`` and ``header_count`` fields can be used for the application to
320 * The ``final_chunk`` field is used to indicate that the application has no more
328 to the application, and the application reports there is no more data to include
334 Websocket resources register an application callback, which is called when a
337 the application takes full control over the socket, i. e. is responsible to
367 processing of the Websocket connection is application-specific, hence outside
374 The application can register an interest in any specific HTTP request headers.
383 Then the application can register headers to be captured, and read the values