Hauke, That is an idea worthy of discussion, but it is tangential to this discussion regarding the issue with routing manager.
Sachin, Yes, it is optional. It is only useful on device with multiple transport. Pat From: Hauke.Mehrtens at lantiq.com [mailto:[email protected]] Sent: Tuesday, September 22, 2015 4:42 AM To: Agrawal, Sachin; Lankswert, Patrick; Schulhof, Gabriel Cc: iotivity-dev at lists.iotivity.org Subject: RE: [dev] Discovery mechanism broken IoTivity needs a config.h header file which gets generated in the build process and contains all the selected options. All header files from IoTivity which have an #ifdef FEATURE_XYZ in it have to include this file. If it is done this way no external application or any sample has to explicitly specifying the same build parameters again, which were used for the main build. The current way will cause more problems later on, especially when people start using IoTivity and only use the library and have their application in an external repository. Hauke From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Agrawal, Sachin Sent: Dienstag, 22. September 2015 00:10 To: Lankswert, Patrick; Schulhof, Gabriel Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Discovery mechanism broken Hi Pat, If we consider it as an optional feature, then it should not be enabled by default. Thanks Sachin From: Lankswert, Patrick Sent: Monday, September 21, 2015 2:58 PM To: Agrawal, Sachin; Schulhof, Gabriel Cc: markus.jung at samsung.com<mailto:markus.jung at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] Discovery mechanism broken Sachin, It looks like we should disable routing manager as the default. Pat From: Agrawal, Sachin Sent: Monday, September 21, 2015 5:50 PM To: Schulhof, Gabriel Cc: Lankswert, Patrick; markus.jung at samsung.com<mailto:markus.jung at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] Discovery mechanism broken Hi Gabriel, A new feature ?routing manager? has been added in master recently which is enabled by default. This feature modifies the definition of OCDevAddr data structure and includes a variable ?routeData? in OCDevAddr. When you compile client and server samples, you are compiling them without that flag and therefore there is a mis-match in the definition of OCDevAddr between your sample and the liboctbstack. If you compile your sample with ?DROUTING_EP, you should see normal results and discovery should work fine. Thanks Sachin From: Schulhof, Gabriel [mailto:[email protected]] Sent: Monday, September 21, 2015 12:36 PM To: Agrawal, Sachin Cc: Lankswert, Patrick; markus.jung at samsung.com<mailto:markus.jung at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Discovery mechanism broken Hey! In 1.0.0-RC1 the payload seems to be null, rather than a security payload. https://gist.github.com/gabrielschulhof/dcb4597683da1f000fc4 HTH, Gabriel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150922/ea861b2c/attachment.html>
