mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-07 17:31:57 +00:00
f4772519d6
Current coap library fails to parse or prepare if packet is more than one fragment. Added support to handle multi fragment packet. Also well-known/core api used to prepare coap packet and send it through net context api immediately. This is goind to be problematic if user doesn't enable net context. Also user can not encrypt coap packets. Now api will return prepared coap packet to application. Application will send it to peer. Jira: ZEP-2210 Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
55 lines
1.0 KiB
C
55 lines
1.0 KiB
C
/*
|
|
* Copyright (c) 2017 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
/**
|
|
* @file
|
|
*
|
|
* @brief CoAP implementation for Zephyr.
|
|
*/
|
|
|
|
#ifndef __LINK_FORMAT_H__
|
|
#define __LINK_FORMAT_H__
|
|
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
/**
|
|
* @addtogroup coap COAP Library
|
|
* @{
|
|
*/
|
|
/**
|
|
* This resource should be added before all other resources that should be
|
|
* included in the responses of the .well-known/core resource.
|
|
*/
|
|
#define COAP_WELL_KNOWN_CORE_PATH \
|
|
((const char * const[]) { ".well-known", "core", NULL })
|
|
|
|
int coap_well_known_core_get(struct coap_resource *resource,
|
|
struct coap_packet *request,
|
|
struct coap_packet *response,
|
|
struct net_pkt *pkt);
|
|
|
|
/**
|
|
* In case you want to add attributes to the resources included in the
|
|
* 'well-known/core' "virtual" resource, the 'user_data' field should point
|
|
* to a valid coap_core_metadata structure.
|
|
*/
|
|
struct coap_core_metadata {
|
|
const char * const *attributes;
|
|
void *user_data;
|
|
};
|
|
|
|
/**
|
|
* @}
|
|
*/
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|
|
|
|
#endif /* __LINK_FORMAT_H__ */
|