All of lore.kernel.org
 help / color / mirror / Atom feed
From: JH <jupiter.hce@gmail.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Anyone tried to build and to use QUIC?
Date: Fri, 2 Aug 2019 21:33:18 +1000	[thread overview]
Message-ID: <CAA=hcWTacFfR9-hgpNTarnZF37L=Zu27+Ri46bay8GjeGskU0Q@mail.gmail.com> (raw)
In-Reply-To: <867c4cd9-27b2-f7b0-63e0-c0a74a261675@windriver.com>

Hi Randy,


On 8/2/19, Randy MacLeod <randy.macleod@windriver.com> wrote:
> On 7/31/19 7:06 AM, JH wrote:
>> Hi,
>>
>> I searched recipes for supporting QUIC, but could not find it. Has
>> anyone tried to build and to use QUIC?
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - JH
>>
>
> Hi,
>
> I presume that you mean QUIC (Quick UDP Internet Connections)
> as in: https://github.com/conght/quic

Correct.

> I also couldn't find an existing recipe using:
>
> https://layers.openembedded.org/layerindex/branch/master/recipes/?q=QUIC
>
> or by a general web search.
>
> Do you have a specific implementation in mind?

I am looking for a small example of Linux C/C++ QUIC client / server
program in socket level to replace TCP socket communication
application. The client will run on an embedded system resource
limited imx6 built from Yocto, the server is running in Ubuntu VM.

> Care to write a recipe and send it in?
> FYI:
>    http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>
> Alternatively contractors and companies are available if you want to go
> that route.

Absolutely, I am actually looking for that right now, contractors or
companies have expertise in both QUIC and Yocto, please contact me.
Appreciate recommendation of information for relevant contractors and
companies.

Thank you very much Randy.

Kind regards,

- JH


      reply	other threads:[~2019-08-02 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 11:06 Anyone tried to build and to use QUIC? JH
2019-08-01 20:54 ` Randy MacLeod
2019-08-02 11:33   ` JH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA=hcWTacFfR9-hgpNTarnZF37L=Zu27+Ri46bay8GjeGskU0Q@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --cc=randy.macleod@windriver.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.