<blockquote>
<p>The only difference between this and the upload queue is whether the POST returns immediately or tries to wait</p>
</blockquote>
<p>Exactly. The only difference is that the queue requires a second call (or even some more of them) to figure out that the status on the server was. I thought that's a bit of an overkill for a change upload that takes seconds rather than minutes in the future. Also, it would probably be more effort on the client side to implement such a queue based protocol, and not compatible with what we have today.</p>
<blockquote>
<p>Well that and that the queue version avoids having to reupload everything on the future calls though again it wouldn't matter if you did, it could just ignore it and return the cached result.</p>
</blockquote>
<p>Well, reuploading won't hurt that much to justify the additional complexity of a queue. Otherwise, it's exactly as you say, ignore the message and return the cached response.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-480496583">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLSkcmjYmOcRLGg20hqlDG0mMzBbCks5veISqgaJpZM4cgFOf">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABWnLTvexVSGLDCveUVZS1etz1cSXHD-ks5veISqgaJpZM4cgFOf.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mmd-osm in #2201: \u003e The only difference between this and the upload queue is whether the POST returns immediately or tries to wait\r\n\r\nExactly. The only difference is that the queue requires a second call (or even some more of them) to figure out that the status on the server was. I thought that's a bit of an overkill for a change upload that takes seconds rather than minutes in the future. Also, it would probably be more effort on the client side to implement such a queue based protocol, and not compatible with what we have today.\r\n\r\n\u003e Well that and that the queue version avoids having to reupload everything on the future calls though again it wouldn't matter if you did, it could just ignore it and return the cached result.\r\n\r\nWell, reuploading won't hurt that much to justify the additional complexity of a queue. Otherwise, it's exactly as you say, ignore the message and return the cached response.\r\n\r\n\r\n"}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-480496583"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-480496583",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-480496583",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>