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; 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; 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; 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/20150921/4e3c3959/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7768 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150921/4e3c3959/attachment.p7s>

Reply via email to