1e47f26d1c
As we are removing net_app and net_pkt based libraries and applications, CoAP legacy based libraries and apps are moved to socket based implementations. So removing legacy CoAP. Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
56 lines
1.1 KiB
C
56 lines
1.1 KiB
C
/*
|
|
* Copyright (c) 2018 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
/**
|
|
* @file
|
|
*
|
|
* @brief CoAP implementation for Zephyr.
|
|
*/
|
|
|
|
#ifndef ZEPHYR_INCLUDE_NET_COAP_LINK_FORMAT_H_
|
|
#define ZEPHYR_INCLUDE_NET_COAP_LINK_FORMAT_H_
|
|
|
|
/**
|
|
* @addtogroup coap COAP Library
|
|
* @{
|
|
*/
|
|
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
/**
|
|
* 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,
|
|
u8_t *data, u16_t len);
|
|
|
|
/**
|
|
* 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 /* ZEPHYR_INCLUDE_NET_COAP_LINK_FORMAT_H_ */
|