Thiago, thanks for the clarification. Yeah, you have a point, I agree with
those reasons though they are more server-related and CoAP module has no one
yet. I was also thinking that having a TP status on CoAP module can help to
mitigate possible API/design problems/inconsistency.
Maurice:
> if DTLS takes too long to implement and CoAP would stay for a very long time
> in TP mode.
It should not, but it's too early/too late given feature-freeze in 2 weeks - so
it's for 5.12.
Could we have CoAP as TP given DTLS will be in 5.12?
Best regards,
Timur.
________________________________
From: Development <[email protected]>
on behalf of Maurice Kalinowski <[email protected]>
Sent: Tuesday, January 16, 2018 8:40:03 AM
To: Thiago Macieira; [email protected]
Subject: Re: [Development] QtCoap: QNAM-like API or not
> > They model their Coap client after QNAM and related classes (like
> > QNetworkRequest/Reply pair).
> >
> > As I understand it now - DTLS or not does not affect this API much -
> > they can later
>
> You don't know that. Until we know how DTLS will work, we won't know if
> there's any impact in the front-end API for CoAP. For example, can you use
> one CoAP server for both encrypted and not encrypted? Multicast and
> unicast?
>
> What's more, we CANNOT release a full CoAP API until it implements DTLS.
> It's just not acceptable to do so otherwise. Therefore, until there's DTLS,
> the
> API is Technology Preview and subject to change. So I don't feel we need to
> review it yet. I have not spent any time myself.
>
[Maurice Kalinowski]
I guess having it as Technology Preview for a first release is the usual way to
go anyways. That way, the API could still be changed afterwards, but also
interested parties could get a first impression and suggest adoptions already,
even though DTLS is not available yet.
Personally, I do not see those two items (missing DTLS, release TP)
conflicting. The only "problem" which might exist, if DTLS takes too long to
implement and CoAP would stay for a very long time in TP mode.
Maurice
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
