Re: Small size of core QUIC library to replace TCP for embedded system

[Jupiter <[e-mail]>]

Hi Lars,

On 7/21/20, Lars Eggert <[e-mail]> wrote:
> if your hardware can run Linux, most of the current open source stacks (see
> https://github.com/quicwg/base-drafts/wiki/Implementations) should be small
> enough to work. But I wouldn't call it an embedded system then...

Sorry for not being clear, I should say Linux embedded system at the
beginning. Although I would say the time for embedded systems with 8M
Flash and 64KRAM has been long gone :-), I still have to manage the
resources for meaning full network stacks and applications.

> But constrained-resource embedded devices at the low end often can't run
> Linux or another full-fledged OS. Many hence link together an application
> with only the required bits of a library OS (RIOT, Zephyr, FreeRTOS &
> derivatives) and run that statically on bare metal.

With all due respect, unless you are working on IoT for tiny devices
cannot run Linux, it is 2020, hardware is cheaper, software
development is expensive, Linux and open source become dominant force
in contemporary embedded system, your Android mobile phone is an
embedded system running Linux :-), Sorry let's stop it, we are too far
off topic.

> You do not need to do this for QUIC, only when you want to run on embedded
> boards that don't have a capable-enough Socket API interface.

Good to know, fair to say your git source is for RTOS statically on
bare metal, I was there a long time before :-).

> It will run on Linux without changes (my public test server runs Ubuntu).

I'll try it, thanks Lars.


jupiter

--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs