On 12/21/18 3:10 PM, Gregg Reynolds wrote: >> interfaces as envisioned by OCF are a stretch in applying the concept >> you see in some object-oriented languages to the OCF API model, and >> didn't ever get explained well. but that's just my opinion as an >> outsider-gadfly type these days :) >> > > See, here's a problem. OCF does not do interfaces. Its a protocol. > "Interfaces" are an implemetation detail. Iotivity has a very wierd > quasi-OO notion of interface. In any case OCF should have no truck with > interfaces.
it does - as I said, it's the object-oriented concept, the one of defining the possible inputs and outputs on a particular view (a view of a resource, in this case), such as the links-list interface which lets you operate only on the links or the batch interface which lets you operate on the batch collection. interface is a horribly overloaded term and I wish OCF had picked a different name for this... I think recent efforts have been to try to call this concept consistently "resource interface" - that may have been a request from the ISO reviewers. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10088): https://lists.iotivity.org/g/iotivity-dev/message/10088 Mute This Topic: https://lists.iotivity.org/mt/28815690/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
