On Tue, May 29, 2018, 7:27 AM Ondrej Tomcik
wrote:
> Hello devs,
>
> In the Kistler, we’re working on the go-coap implementation which supports
> TCP with TLS and is compatible with the IoTivity.
>
Not to rain on your parade, but how is your project different from these?
https://github.com/dusti
egards,
>Scott
>
>-Original Message-
>From: iotivity-dev@lists.iotivity.org
>[mailto:iotivity-dev@lists.iotivity.org] On Behalf Of Thiago Macieira
>Sent: Friday, June 1, 2018 4:54 PM
>To: Gregg Reynolds
>Cc: iotivity-dev
>Subject: Re: [dev] coap-go repository
&g
#x27;m definitely interested in
checking out that flutter app you mentioned, can you provide a link to it?
Regards,
Scott
-Original Message-
From: iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.iotivity.org]
On Behalf Of Thiago Macieira
Sent: Friday, June 1, 2018 4:54 PM
To:
On Friday, 1 June 2018 13:24:32 PDT Gregg Reynolds wrote:
> > I don't think this should be in IoTivity.
>
> How is this different from the cloud thing? That goes wy beyond
> Iotivity. If, strictly speaking, iotivity is about a reference
> implementation of the OCF protocol, then what is a proj
On Fri, Jun 1, 2018, 9:08 AM Thiago Macieira
wrote:
> On Thursday, 31 May 2018 22:13:32 PDT Ondrej Tomcik wrote:
> > I expected that - "implementation of the coap in the golang" is clear
> > enough, as it is standardized protocol
> https://tools.ietf.org/html/rfc7252
> > .
> >
> > Or, if it was n
On Thursday, 31 May 2018 22:13:32 PDT Ondrej Tomcik wrote:
> I expected that - "implementation of the coap in the golang" is clear
> enough, as it is standardized protocol https://tools.ietf.org/html/rfc7252
> .
>
> Or, if it was not - "go-coap implementation which supports TCP with TLS and
> is c
> Please explain then what will be in this repository, why it should belong in
> IoTivity, who will be responsible for it (that is, who the Maintainer will
> be), and propose a proper name for it.
> I think I've asked you to explain the goals at least three times and I still
> don't get what y
From: iotivity-dev@lists.iotivity.org On
Behalf Of Scott King
Sent: Thursday, May 31, 2018 3:33 PM
To: iotivity-dev@lists.iotivity.org; Thiago Macieira
Subject: Re: [dev] coap-go repository
Thiago,
The iotivity project already maintains its own fork of libcoap, what is
different about doing
the high level goals and foundational
assumptions for our respective arguments, that the technical decisions will
become much more obvious and less controversial.
Best regards,
Scott
From: Thiago Macieira
Sent: Thursday, May 31, 3:38 PM
Subject: Re: [dev] coap-go repository
To: iotivity-dev@lists.i
On Thursday, 31 May 2018 11:55:28 PDT Ondrej Tomcik wrote:
> Who said it is only TCP implementation gentlemen? I was talking about TCP
> Cloud. Or as Gregg wrote, let's call it differently. I am using this
> strange name just because that's how the POC in the /iotivity/cloud was
> named by the Sams
8 8:34 PM
To: Thiago Macieira; iotivity-dev@lists.iotivity.org
Cc: Tomcik Ondrej
Subject: RE: [dev] coap-go repository
+1 to what Thiago said. If this is just implementing the COAP over TCP RFC, it
doesn't belong in the iotivity project, it should be in its own project that
can be refere
ieira
Sent: Thursday, May 31, 2018 6:53 AM
To: iotivity-dev@lists.iotivity.org
Cc: Ondrej Tomcik
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 refere
age-
> From: Thiago Macieira [mailto:thiago.macie...@intel.com]
> Sent: Thursday, May 31, 2018 3:54 PM
> To: iotivity-dev@lists.iotivity.org
> Cc: Tomcik Ondrej
> Subject: Re: [dev] coap-go repository
>
> On Wednesday, 30 May 2018 22:40:42 PDT Ondrej Tomcik wrote:
> > It's
sday, May 31, 2018 3:54 PM
To: iotivity-dev@lists.iotivity.org
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 Co
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
: iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.iotivity.org]
On Behalf Of Thiago Macieira
Sent: Thursday, May 31, 2018 7:31 AM
To: iotivity-dev@lists.iotivity.org
Subject: Re: [dev] coap-go repository
On Tuesday, 29 May 2018 05:27:03 PDT Ondrej Tomcik wrote:
> Hello devs,
> In th
On Tuesday, 29 May 2018 05:27:03 PDT Ondrej Tomcik wrote:
> Hello devs,
> In the Kistler, we're working on the go-coap implementation which supports
> TCP with TLS and is compatible with the IoTivity. This is the prerequisite
> for the new cloud we're working on.
>
> Would like to ask you to creat
Hello devs,
In the Kistler, we're working on the go-coap implementation which supports TCP
with TLS and is compatible with the IoTivity.
This is the prerequisite for the new cloud we're working on.
Would like to ask you to create go-coap project in the IoTivity and inform you
that we're taking r
18 matches
Mail list logo
