Lines Matching +full:post +full:- +full:release
2 * coap_resource.h -- generic resource handling
4 * Copyright (C) 2010,2011,2014-2023 Olaf Bergmann <bergmann@tzi.org>
6 * SPDX-License-Identifier: BSD-2-Clause
49 * Observe Notifications will be sent non-confirmable by default. RFC 7641
51 * https://rfc-editor.org/rfc/rfc7641#section-4.5
58 * https://rfc-editor.org/rfc/rfc7641#section-4.5
63 * Observe Notifications will always be sent non-confirmable. This is in
65 * https://rfc-editor.org/rfc/rfc7641#section-4.5
68 * https://rfc-editor.org/rfc/rfc8782#section-4.4.2.1
74 * https://rfc-editor.org/rfc/rfc7252#section-11.3
75 * https://rfc-editor.org/rfc/rfc7390#section-2.8
76 * https://datatracker.ietf.org/doc/html/draft-ietf-core-groupcomm-bis-06.txt#section-3.6
77 * Note: ".well-known/core" always supports multicast.
86 * https://rfc-editor.org/rfc/rfc7252#section-8.2
87 * https://rfc-editor.org/rfc/rfc7390#section-2.8
88 * https://datatracker.ietf.org/doc/html/draft-ietf-core-groupcomm-bis-06.txt#section-3.6
95 * (overridden by RFC7969 No-Response option) for multicast requests.
96 * https://rfc-editor.org/rfc/rfc7390#section-2.7
97 * https://datatracker.ietf.org/doc/html/draft-ietf-core-groupcomm-bis-06.txt#section-3.1.2
104 * RFC7969 No-Response option) for multicast requests.
105 * https://rfc-editor.org/rfc/rfc7390#section-2.7
106 * https://datatracker.ietf.org/doc/html/draft-ietf-core-groupcomm-bis-06.txt#section-3.1.2
113 * RFC7969 No-Response option) for multicast requests.
114 * https://rfc-editor.org/rfc/rfc7390#section-2.7
115 * https://datatracker.ietf.org/doc/html/draft-ietf-core-groupcomm-bis-06.txt#section-3.1.2
122 * RFC7969 No-Response option) for multicast requests.
123 * https://rfc-editor.org/rfc/rfc7390#section-2.7
124 * https://datatracker.ietf.org/doc/html/draft-ietf-core-groupcomm-bis-06.txt#section-3.1.2
158 * not normally required - e.g. just "full/path/for/resource".
165 * observe notifications will be sent as non-confirmable,
170 * non-confirmable.
183 * POST, GET, DELETE etc. handlers can be added to this resource. It is the
189 * Note: There can only be one unknown resource handler per context - attaching
193 * - a separate resource needs to be created by the PUT (or POST)
199 * unknown Uri-Path.
211 * POST, GET, DELETE etc. handlers can be added to this resource. It is the
217 * Note: There can only be one unknown resource handler per context - attaching
221 * - a separate resource needs to be created by the PUT (or POST)
227 * unknown Uri-Path.
240 * Note: There can only be one proxy resource handler per context - attaching
243 * @param handler The PUT/POST/GET etc. handler that handles all request types.
259 * Note: There can only be one proxy resource handler per context - attaching
262 * @param handler The PUT/POST/GET etc. handler that handles all request types.
309 * Sets the user_data. The user_data is exclusively used by the library-user
319 * Gets the user_data. The user_data is exclusively used by the library-user
329 * Definition of release resource user_data callback function
335 * to release the data held in the resource's user_data.
337 * @param context The context to associate the release callback with
408 * @param flags Flags for memory management (in particular release of
466 * Writes a description of this resource in link-format to given text buffer. @p