Re: Deprecating and removing net-app based APIs
On Wed, 16 Jan 2019 18:45:34 +0200
"Jukka Rissanen" <email@example.com> wrote:
Hi all,+1 for deprecation, -1 for removal in 1.14. 1.14 is supposed to be LTS
release, and we shouldn't leave users who used prior versions of Zephyr
in the cold with the first LTS which removes a lot of familiar APIs
(even without providing replacements, as discussed below).
Over a year ago, it was agreed among network API users, thatGood. But one year isn't that big a timeframe. Some higher-level
network libs were converted to sockets, some not.
I sent a mail in the beginning of December 2018  about HTTPWell, I responded to it with some proposals, and that's were it stands.
There should be discussion on the way to approach. It's a bit of
wishful thinking that someone will pop up at them moment that we
asked. Likewise, I'd call it a leap of faith that someone will start
to work on it just to not lose HTTP libs from Zephyr - this doesn't
guarantee quality of implementation, nor even that it'll be merged (we
had cases like "oh, you wrote something? but that's not what we
need"). Again, discussion and sustainable approach.
This removal of these APIs also means that there wouldThat would be the reason to not remove them, and definitely not for
It is important that we do not have multiple implementations for the--
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog