Skip to content

Commit

Permalink
Script updating archive at 2021-07-27T19:02:35Z. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jul 27, 2021
1 parent 2001ed6 commit 9ff351d
Showing 1 changed file with 55 additions and 8 deletions.
63 changes: 55 additions & 8 deletions archive.json
@@ -1,6 +1,6 @@
{
"magic": "E!vIA5L86J2I",
"timestamp": "2021-07-22T23:06:58.055084+00:00",
"timestamp": "2021-07-27T19:02:33.828532+00:00",
"repo": "quicwg/datagram",
"labels": [
{
Expand Down Expand Up @@ -1408,6 +1408,37 @@
"updatedAt": "2021-07-20T21:13:24Z"
}
]
},
{
"number": 41,
"id": "MDU6SXNzdWU5NTM4NTQ5OTI=",
"title": "Is it obvious that Datagram frame can be aggregated in the same QUIC packet",
"url": "https://github.com/quicwg/datagram/issues/41",
"state": "OPEN",
"author": "gloinul",
"authorAssociation": "NONE",
"assignees": [],
"labels": [],
"body": "I find no discussion about aggregating DATAGRAM frames in the same QUIC packets, with other DATAGRAM frames or other types. Is that so obvious that it is possible that it doesn't need mentioning?\r\n\r\nI would be slightly worried that an QUIC stack that aggregate may cause fate sharing between different datagram frames, which the application wasn't expecting. In a classical UDP application clearly doing two calls for UDP packets will create two different packets. Two calls to transmit Datagram frames may not cause multiple QUIC packets to be sent, which is usually for the good. However, it goes back to maybe be clear that this may occurr, and a question if API needs consideration to indicate if aggregation is fine or not?",
"createdAt": "2021-07-27T12:56:58Z",
"updatedAt": "2021-07-27T18:52:07Z",
"closedAt": null,
"comments": [
{
"author": "DavidSchinazi",
"authorAssociation": "CONTRIBUTOR",
"body": "We originally had text for this, but folks pointed out that we can't make recommendations that apply to all use cases: some might want fate sharing while some might not. It's probably best to leave this up to the application.",
"createdAt": "2021-07-27T16:16:34Z",
"updatedAt": "2021-07-27T16:16:34Z"
},
{
"author": "gloinul",
"authorAssociation": "NONE",
"body": "So I don't think recommendations are necessary. I think bringing up the issue and the potential need for an API to indicate on per datagram if it is okay for this to be aggregated with other datagrams would be sufficient. \r\n",
"createdAt": "2021-07-27T18:52:07Z",
"updatedAt": "2021-07-27T18:52:07Z"
}
]
}
],
"pulls": [
Expand Down Expand Up @@ -3082,26 +3113,42 @@
"id": "MDExOlB1bGxSZXF1ZXN0Njk1NTYzNjQ1",
"title": "Acknowledge Victor",
"url": "https://github.com/quicwg/datagram/pull/40",
"state": "OPEN",
"state": "MERGED",
"author": "DavidSchinazi",
"authorAssociation": "CONTRIBUTOR",
"assignees": [],
"labels": [],
"body": "",
"createdAt": "2021-07-22T23:06:43Z",
"updatedAt": "2021-07-22T23:06:47Z",
"updatedAt": "2021-07-27T19:02:11Z",
"baseRepository": "quicwg/datagram",
"baseRefName": "main",
"baseRefOid": "5adf366e4414318bfb2e45c806c06ac2b9e49b4f",
"headRepository": "quicwg/datagram",
"headRefName": "vvv",
"headRefOid": "e8728c40f035f75b764537dec096712783c6ba1d",
"closedAt": null,
"mergedAt": null,
"mergedBy": null,
"mergeCommit": null,
"closedAt": "2021-07-27T19:02:10Z",
"mergedAt": "2021-07-27T19:02:10Z",
"mergedBy": "tfpauly",
"mergeCommit": {
"oid": "67b81e9dcf21fb83f66c750ff4b9c05729042f98"
},
"comments": [],
"reviews": []
"reviews": [
{
"id": "MDE3OlB1bGxSZXF1ZXN0UmV2aWV3NzE2Mjc3MTcx",
"commit": {
"abbreviatedOid": "e8728c4"
},
"author": "tfpauly",
"authorAssociation": "CONTRIBUTOR",
"state": "APPROVED",
"body": "",
"createdAt": "2021-07-27T19:02:05Z",
"updatedAt": "2021-07-27T19:02:05Z",
"comments": []
}
]
}
]
}

0 comments on commit 9ff351d

Please sign in to comment.