Note: This was originally posted in the Development forums, but I re-posted it here because it felt like the wrong place to post this, and it wasn't garnering a lot of attention.
From the way I see it, osu! queues scores to be resubmitted in "power of two" minute intervals if it doesn't work properly. If this is the case, I wondered why it couldn't just be held in queue and submitted once it detects that a stable connection is established?
Example of (what I think is) the current score submission queueing behavior:
A submission is attempted for a recent beatmap score. If the submission fails, it is queued and scheduled to resubmit in one minute. If it fails again, it is scheduled to resubmit in two minutes. This continues for four minutes, eight minutes, 16, 32, 64, 128. This is kind of an inefficient way to handle the queueing of score submission.
Example of theoretically better(?) queueing:
A submission is attempted for a recent beatmap score. If the submission fails, it is queued and scheduled to resubmit in one minute. If it fails again, it is queued and waits for when a new score successfully submits. Once the submission for a new score does work, the queued scores will be submitted, one after another.
This would benefit those who have unstable connection or lost connection for extended periods of time. Of course, this does not negate any mechanics regarding the dismissal of scores from the queue (time limit, leaving osu!, etc.).
I'd love to hear your opinion on this, whether you're a player with Reese-level fiber optic connections or a player in an undeveloped country with 0.3 mbps speed. We all eventually suffer some form of downtime, right?
From the way I see it, osu! queues scores to be resubmitted in "power of two" minute intervals if it doesn't work properly. If this is the case, I wondered why it couldn't just be held in queue and submitted once it detects that a stable connection is established?
Example of (what I think is) the current score submission queueing behavior:
A submission is attempted for a recent beatmap score. If the submission fails, it is queued and scheduled to resubmit in one minute. If it fails again, it is scheduled to resubmit in two minutes. This continues for four minutes, eight minutes, 16, 32, 64, 128. This is kind of an inefficient way to handle the queueing of score submission.
Example of theoretically better(?) queueing:
A submission is attempted for a recent beatmap score. If the submission fails, it is queued and scheduled to resubmit in one minute. If it fails again, it is queued and waits for when a new score successfully submits. Once the submission for a new score does work, the queued scores will be submitted, one after another.
This would benefit those who have unstable connection or lost connection for extended periods of time. Of course, this does not negate any mechanics regarding the dismissal of scores from the queue (time limit, leaving osu!, etc.).
I'd love to hear your opinion on this, whether you're a player with Reese-level fiber optic connections or a player in an undeveloped country with 0.3 mbps speed. We all eventually suffer some form of downtime, right?
