Date: Thu, 12 Apr 2018 00:33:35 +0000 (UTC)
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abc8bb2e18c1779107fca073fcbbae1477195f725792cf0000000116e66b5f92a169ce12ae7fcb@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1287/380637430@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1287@github.com>
References: <quicwg/base-drafts/issues/1287@github.com>
Subject: Re: [quicwg/base-drafts] Order of Compound Packets (#1287)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5acea95fb1493_43e42b22fdcdeed4735987";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/tuXDBHw_oXy9Q4asZhUs1RaTM70>

----==_mimepart_5acea95fb1493_43e42b22fdcdeed4735987
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I agree that the compound packets are pain, programming-wise.  Now one has to have "real packets" versus "QUIC packets" or do something else equally odd.

I'd go as far as to say that there can be at most one long-header packet in a compound packet.  (Is there a use case for having more than one?)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1287#issuecomment-380637430
----==_mimepart_5acea95fb1493_43e42b22fdcdeed4735987
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I agree that the compound packets are pain, programming-wise.  Now one h=
as to have "real packets" versus "QUIC packets" or do something else equall=
y odd.</p>
<p>I'd go as far as to say that there can be at most one long-header packet=
 in a compound packet.  (Is there a use case for having more than one?)</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda=
sh;<br />You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, <a href=3D"https://github.com/quicwg/bas=
e-drafts/issues/1287#issuecomment-380637430">view it on GitHub</a>, or <a h=
ref=3D"https://github.com/notifications/unsubscribe-auth/AWbkq0bp4A1G8UEDT0=
F-5bV0q0V7ZV1bks5tnqDfgaJpZM4TQeWh">mute the thread</a>.<img src=3D"https:/=
/github.com/notifications/beacon/AWbkqyphHWaHl8z31XRp1bRhrB0caj6Lks5tnqDfga=
JpZM4TQeWh.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewAction=
">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/issu=
es/1287#issuecomment-380637430"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></meta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_version"=
:"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"Gi=
tHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg=
/base-drafts","subtitle":"GitHub repository","main_image_url":"https://clou=
d.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290=
892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/asset=
s/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name=
":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates=
":{"snippets":[{"icon":"PERSON","message":"@dtikhonov in #1287: I agree tha=
t the compound packets are pain, programming-wise.  Now one has to have \"r=
eal packets\" versus \"QUIC packets\" or do something else equally odd.\r\n=
\r\nI'd go as far as to say that there can be at most one long-header packe=
t in a compound packet.  (Is there a use case for having more than one?)"}]=
,"action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts=
/issues/1287#issuecomment-380637430"}}}</script>=

----==_mimepart_5acea95fb1493_43e42b22fdcdeed4735987--