-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from Iotivity for draft-ietf-core-coap-tcp-tls and cross-platform support #47
base: develop
Are you sure you want to change the base?
Conversation
Change-Id: Idddee819530e8eb497a8abf72aa1f94a7b30d40b Signed-off-by: Dave Thaler <[email protected]>
Change-Id: Idddee819530e8eb497a8abf72aa1f94a7b30d40b Signed-off-by: Dave Thaler <[email protected]>
…elop Change-Id: I92dee387c3d58b2d348366e923be007efe833b3e
…elop Change-Id: I92dee387c3d58b2d348366e923be007efe833b3e
…elop Change-Id: Ib573dd192fdb84622e9bd24b2e5932dad1dd9501
…elop Change-Id: Ib573dd192fdb84622e9bd24b2e5932dad1dd9501
Change-Id: I41875348e9667a999bbb223bca3d99d4201fc8fb Signed-off-by: Dave Thaler <[email protected]>
Change-Id: I41875348e9667a999bbb223bca3d99d4201fc8fb Signed-off-by: Dave Thaler <[email protected]>
…elop Change-Id: I02a8a520b3743f13b5ab957773c012587263fc83
Thanks, this contribution is highly appreciated. Unfortunately, Travis reports this PR to break the Linux port. It would be great if you could take a look into that issue. |
Signed-off-by: Dave Thaler <[email protected]>
Just pushed a fix for the bug due to a bad merge |
Signed-off-by: Dave Thaler <[email protected]>
My apologies -- I have pushed an old patch to src/block.c which now breaks this PR. |
src/net.c
Outdated
@@ -554,7 +554,7 @@ coap_send_ack(coap_context_t *context, | |||
return result; | |||
} | |||
|
|||
#if defined(WITH_POSIX) || defined(WITH_CONTIKI) | |||
#if !defined(WITH_LWIP) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't use negative logic here and let that check as it is, it's hard to figure out for some not well knowledge people what !WITH_LWIP means!
Signed-off-by: Dave Thaler <[email protected]>
Signed-off-by: Dave Thaler <[email protected]>
Is this task tracked on iotivity tracker ? I see there is a conflict to be resolved |
Yes https://jira.iotivity.org/browse/IOT-1072 tracks the iotivity task. IoTivity already uses this branch temporarily on Windows and other OS's will start snapping to it after merge. I will rebase to fix the conflict. |
Signed-off-by: Dave Thaler <[email protected]>
Signed-off-by: Dave Thaler <[email protected]>
Signed-off-by: Dave Thaler <[email protected]>
Signed-off-by: Dave Thaler <[email protected]>
I believe all feedback so far has been addressed. Would like to see this PR merged so iotivity can start depending on the upstream branch. Let me know if there are any more blocking issues. |
Hello Dave, first thanks for contributing! Some comments below. Beside the build issues I'd like to see better commit messages, please see and note https://github.com/obgm/libcoap/blob/develop/CONTRIBUTE#L161 Please don't mix extensions of specific changes to the header files or small adoptions within the header files with improving of the API documentation in other parts, split them of into more easier to understand changes. Also try to decrease merge commit from upstream much as possible, normally there shouldn't be even one as you should use Please don't be disappointed, such big changes need time to get integrated. Maybe you can split the PR into more than one PR if it turns out there are some thematic changes. If I read your first post this PR is including two things, tcp-tls and cross-platform support for Windows. For the latter it would be good to have build support than. Regards |
FYI, The changes in this PR have been done in IoTivity's fork of this repo across the course of a couple years by a bunch of people. I am merely pushing them here, I am not authoritative for all the original changes, just trying to get rid of a forked copy and make contributions in the future to a single place rather than IoTivity folks continuing to make changes to their own fork. I will do what I can, but I may not be able to answer all questions myself. Pushing back just means that tons of devices (like all the devices Samsung ships) will continue to use a separate fork not the master GitHub version. |
Hi as Samsung OSG developer I believe it's better for iotivity to be the most aligned possible with upstream, thanks @dthaler for your efforts. |
Dave, thanks for a little bit explanation about the details of this PR. I think Olaf is of course willing to pull your changes in this PR. But we need to puzzle the various things out into parts that are logical things. That for one simple reason, not only we need to understand what the changes are about. So how to get further here? I'd suggest to do the easy parts first, for example changes that are made by you or direct working people. Olaf has released the recent state of libcoap as version 4.1.2 so we can start now mostly lazy with new changes. |
Apparently caused by an incorrect merge. Signed-off-by: Dan Mihai <[email protected]>
Fix pdu length truncation
Signed-off-by: Dave Thaler <[email protected]>
This commit makes sure libcoap doesn't generate any W4 warnings when building with a Visual Studion 2013 and 2015 compiler.
Making sure that "if" statements have opening brackets on the same line to fit the with the rest of the code.
Removing W4 warnings
Any news on this? |
It certainly is high on my priority list but sorting stuff out will take some time. |
This change contains only packet format changes in the library to support coap+ws and coaps+ws. Signed-off-by: G S Senthil Kumar <[email protected]>
…p on windows. Merge changes from PR obgm#47 related to windows platform support. Add full windows platform support including correct error checking and working regression tests and examples. Remove need to build applications using libcoap with -DWITH_POSIX and to include coap_config.h. This applies to the examples as well.
…p on windows. Merge changes from PR obgm#47 related to windows platform support. Add full windows platform support including correct error checking and working regression tests and examples. Remove need to build applications using libcoap with -DWITH_POSIX and to include coap_config.h. This applies to the examples as well. # Conflicts: # examples/client.c # examples/coap-rd.c # examples/coap-server.c # include/coap/address.h # include/coap/coap_io.h # include/coap/net.h # include/coap/prng.h # src/address.c # src/block.c # src/net.c # src/pdu.c # src/platform/posix/coap_io.c # src/resource.c
Added CoAP over WebSocket PDU support.
Update pdu.c
Adding API to add token to empty message
@dthaler I am having trouble understanding what these changes are about. For example, commit 5f2d238 introduces a function |
The function coap_pdu_parse2() as changed by iotivity patches has a block of code bracketed by #if defined(WITH_TCP) || defined(WITH_WS) the problem is this block contains a reference to a structure member that is defined only if WITH_WS is defined, and it is possible to build this code in iotivity in the presence of WITH_TCP and the absence of WITH_WS. Whether that should ever happen is a separate question; the change keeps these two conditions separate so this can be used in the iotivity CI system which does build some targets in the way noted. Signed-off-by: Mats Wichmann <[email protected]>
Fix for where WITH_TCP is defined, WITH_WS is not.
These changes were already in the Iotivity code base, and we're trying to unfork libcoap and have iotivity just use the regular libcoap library. These changes include support for draft-ietf-core-coap-tcp-tls and some cross-platform fixes (e.g., to also run on Windows).