On Thursday 26 March 2015 12:22:44 ??? wrote: > Regarding the Primitive service Protocol Plugin Manager, You seems to have > different expectation from current implementation. > OIC Resource point of view, PPM does not provide additional functionality > yet. > PPM does not have any mechanism related with this feature that is > PPM ?framework will map the different property names and values back > onto a standardized and richer API? > Resource Request Handling is up to the Protocol plugin developer?s role. > > However, PPM provides help the lifecycle management of that Resource > Server, more specifically, how to invoke That resource server. > Furthermore, we can design the AllSeen generic Protocol plugin which enable > property and value mapping for each specific resource type might be done > thru configuration file setting. > > Summarizing my opinion > > : From the view of resource handling thru the standardized and supportable > > API, Option 2, 3 same. > However, Option3 will provide the lifecycle management of that resource.
Hi Uze I agree that option 1 is not useful, so we can ignore it. I also agree that option 2 is useful and it might make sense to implement it. The question I have is whether our objective is to stop there or whether it is to go to option 3. Can you clarify? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
