Thiago, One of my obligations is to deliver a specification compliant stack. The routing manager is not based on any standard that I am aware of. We are free to add anything to iotivity, but to meet the standards-based obligation, I need to be able to build a version of the core framework that adheres to the standard. Adding non-standard options from within the stack is a problem.
In the design discussions, it was said expressly that the routing manager features would be optional. So, what was promised was not delivered. It looks like a number of new issues in the stack are a result of the routing manager feature which was not a required feature, but now threatens the delivery of v1.0. Abhishek, Do we have a test plan for the routing manager and have you done a full regression of the stack from the SDK layer to validate this code base? Pat > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Tuesday, September 22, 2015 12:25 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Discovery mechanism broken > > On Tuesday 22 September 2015 14:22:18 Lankswert, Patrick wrote: > > Abhishek, > > > > Then why provide an option for ROUTING=OFF in the first place? > > That option was removed. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
