Remove those from Makefiles and testcase.ini, we now support unified kernel
only and sanitycheck script now knows how to deal with this.
Change-Id: I853ebcadfa7b56a4de5737d95f2ba096babb2e13
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
The KNOWN_ISSUES file describes issues and workarounds for the NATS
and DNS sample applications.
Change-Id: I9a33a82073707dbdd4109e0740108b99c42ad772
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
According to last comments posted in ZEP-632, the unref routine must
be called only when net_send reports an error.
Jira: ZEP-632
Change-Id: I11553edf2c7d686c3e58617c2e05b6f18962955e
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
README files are updated to include information about the
warnings displayed by the compiler.
Applications affected: DNS, NATS and MQTT.
Jira: ZEP-681
Change-Id: I482c3bbf37c5d9af3bb43b7ef5e58957bac2852a
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
The zero bytes hack to connect was deprecated by last
commits, so now we send 1 byte initialized to 0 :).
Jira: ZEP-612
Change-Id: Ie9e65fad3945d0babc4287e287be3aa57d68ed5a
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
This patch adds a README file describing the known-limitations of our
implementation.
Change-Id: I174db79783861f145ae224eca86f3fe4968e0205
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
This patch standardizes the return codes:
- 0 on success
- -EIO on network error
- -EINVAL if an invalid parameter was passed as argument or
received from the server
API documentation is also updated to reflect those changes.
Change-Id: I076d195fde7c6b32b4a52454f312fb8cd8ce2332
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
- Add TCP/IPv4 routines to this sample.
- Add a testcase.ini file.
This NATS sample code demonstrates how to implement a NATS subscriber
application.
Change-Id: I25a7465b7163a09a0163859076a97b1e258a06f1
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
- Add TCP/IPv4 routines to this sample.
- Add a testcase.ini file.
This NATS sample code demonstrates how to implement a NATS publisher
application.
Change-Id: Ifeac3bf03b7febafcee927b1d2ec256685885fd8
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
This sample code demonstrates how to write a NATS subscriber
application. Code is self-documented and a README file is also
included.
This sample code uses the netz API.
The NATS protocol specification is available at:
http://nats.io/documentation/internals/nats-protocol/
Origin: Original
Jira: ZEP-415
Jira: ZEP-573
Jira: ZEP-597
Change-Id: I4b7e56bb6c2a934012b33039ea5b313b14f3b4c5
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
This sample code demonstrates how to write a NATS publisher
application. Code is self-documented and a README file is also
included.
This sample code uses the netz API.
The NATS protocol specification is available at:
http://nats.io/documentation/internals/nats-protocol/
Origin: Original
Jira: ZEP-415
Jira: ZEP-573
Jira: ZEP-596
Change-Id: Ieb6e6e5f9bd48f34246b6d8c1bd9af3bbbe016bb
Signed-off-by: Flavio Santes <flavio.santes@intel.com>
Anas Nashif