On 12/28/18 1:01 PM, Gregg Reynolds wrote: ted. > > interface > >> is a horribly overloaded term and I wish OCF had picked a >> different name for this > > > Not just overloaded. Plain wrong. A better name would be "capability". It > really has nothing to do with oo or interfaces. If your resource does not > support the write "interface", you cannot write to it. That's a permission > idea, has nothing to do with the concept "interface", afaik. > > I suspect this reflects a basic confusion about APIs v. Protocols. > "Interface" is largely meaningless with respect to comm protocols, imho.
something like is this what I believe the guy who came up with that concept for the OCF specs was thinking of: https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/interfaces/index -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10105): https://lists.iotivity.org/g/iotivity-dev/message/10105 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] -=-=-=-=-=-=-=-=-=-=-=-
