zephyr/subsys/net/lib/Kbuild

obj-$(CONFIG_ZOAP) += zoap/
obj-$(CONFIG_DNS_RESOLVER) += dns/
obj-$(CONFIG_MQTT_LIB) += mqtt/
obj-$(CONFIG_HTTP) += http/
iot/dns: Add DNS Client support for Zephyr This commit adds support the DNS client API on top of the new native IP stack. Some features of this implementation are: - Support for IPv4 and IPv6 - Support for multiple concurrent queries. A net_buf structure is required per context. See the DNS_RESOLVER_ADDITIONAL_BUF_CTR configuration variable Origin: Original Jira: ZEP-793 Jira: ZEP-855 Jira: ZEP-975 Change-Id: I351a636462a1b78a412c9bce1ef3cd0fa6223a52 Signed-off-by: Flavio Santes <flavio.santes@intel.com> 2016-10-06 13:07:48 +08:00			`obj-$(CONFIG_ZOAP) += zoap/`
			`obj-$(CONFIG_DNS_RESOLVER) += dns/`
iot: Add MQTT v3.1.1 packet handling support for Zephyr This commit adds support for the MQTT protocol v3.1.1. Specifically, this commit allows a Zephyr application to create the following MQTT messages: CONNACK, CONNECT, PUBLISH, PUBACK, PUBREC, PUBREL, PUBCOMP, UNSUBACK, SUBSCRIBE, SUBACK, UNSUBSCRIBE, PINGREQ, PINGRESP, and DISCONNECT. Furthermore, the following messages can be parsed by the routines provided by this commit: CONNACK, CONNECT, PUBLISH, PUBACK, PUBREC, PUBREL, PUBCOMP, UNSUBACK, SUBSCRIBE, SUBACK, PINGREQ, PINGRESP and DISCONNECT. NOTE: client behavior (routines with network access) and QoS will be integrated in future patches. The MQTT v3.1.1 specification can be found at: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html Origin: Original Jira: ZEP-365 Jira: ZEP-591 Jira: ZEP-856 Change-Id: Ie0c179370cea22f7554564692bc426a8d5c419d2 Signed-off-by: Flavio Santes <flavio.santes@intel.com> 2016-11-08 12:37:19 +08:00			`obj-$(CONFIG_MQTT_LIB) += mqtt/`
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com> 2017-02-22 05:02:00 +08:00			`obj-$(CONFIG_HTTP) += http/`