The TCP port number discovery based UDP multicast message
authorhyuna0213.jo <hyuna0213.jo@samsung.com>
Thu, 31 Mar 2016 08:21:06 +0000 (17:21 +0900)
committerJon A. Cruz <jon@joncruz.org>
Wed, 27 Apr 2016 06:00:46 +0000 (06:00 +0000)
commit9699440dbf08028b522b47dc327be9453742c08e
tree827b4dd77f75f5fb9f778877fb27c355d563f946
parent8593cd10aca36f4f400f92470508055d8a05909b
The TCP port number discovery based UDP multicast message

The TCP port number will be part of the discovery payload.
so the response to the UDP multicast message, should be an UDP unicast
reply containing the TCP port number if TCP adapter is activated.
After receiving the discovery response, the client can use TCP port
number to communicate with the server via CoAP/TCP.

- added tcp port value in policy of discovery payload
- the dynamic use of tcp server port in TCP adapter
- TCP adapter changes to support IPv6

Change-Id: Ie93361abec0287f0f600a791a58e41cf5b381892
Signed-off-by: hyuna0213.jo <hyuna0213.jo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/7483
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Jon A. Cruz <jon@joncruz.org>
resource/csdk/connectivity/api/cacommon.h
resource/csdk/connectivity/src/tcp_adapter/catcpadapter.c
resource/csdk/connectivity/src/tcp_adapter/catcpserver.c
resource/csdk/stack/include/ocpayload.h
resource/csdk/stack/include/octypes.h
resource/csdk/stack/src/ocpayload.c
resource/csdk/stack/src/ocpayloadconvert.c
resource/csdk/stack/src/ocpayloadparse.c
resource/csdk/stack/src/ocresource.c
resource/csdk/stack/src/ocstack.c
resource/include/OCSerialization.h