On Thu, May 31, 2018, 9:02 AM Ondrej Tomcik <[email protected]> wrote:
> Cloud is already part of the specification. Library will be used in the > cloud implementation which will follow OCF specification. > Hi Ondrej, Here's the problem I'm having: I don't know what you mean. What is "cloud"? What does "will follow OCF specification" mean? Note that UDP support is not optional for OCF, afaik. I could be wrong about that, but if not an implementation that supports only tcp and not UDP could not be considered OCF-compliant. If OCF support is secondary in your project, why should it be hosted by the main OCF website? Fwiw I'm not against it in principle, but iotivity is sufficiently chaotic already. Gregg > It would make sense to host the CoAP protocol code in IoTivity only if it > was developed closely with the OCF implementation on top. > It will, but only the cloud part at this moment. That's what I wrote: "It > will be afterwards referenced and used as TCP CoAP server in the new cloud." > > >> We're currently not thinking about the OCF protocol implementation, but > who knows how it evolves. > I just meant that we don't have a plan to work on device side currently. > But this library can be used also on device side and who knows how we will > continue. > > So I think it is a good idea to have it in the IoTivity group. > > > -----Original Message----- > From: Thiago Macieira [mailto:[email protected]] > Sent: Thursday, May 31, 2018 3:54 PM > To: [email protected] > Cc: Tomcik Ondrej > Subject: Re: [dev] coap-go repository > > On Wednesday, 30 May 2018 22:40:42 PDT Ondrej Tomcik wrote: > > It's going to implement only the coap protocol in the Golang. > > It will be afterwards referenced and used as TCP CoAP server in the new > > cloud. > > > > We're currently not thinking about the OCF protocol implementation, but > who > > knows how it evolves. > > If you're not going to implement the OCF protocol, my recommendation is > that > you host it elsewhere, like GitHub or GitLab. It would make sense to host > the > CoAP protocol code in IoTivity only if it was developed closely with the > OCF > implementation on top. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > > > > > >
