←back to thread

78 points cloudmanager | 1 comments | | HN request time: 0s | source
Show context
Kerrick ◴[] No.45342394[source]
Removing choice is fine, but people will want to know what number they'll get if they order right now. Even if you can't or won't show the next rock, show the next number.
replies(2): >>45342422 #>>45342752 #
windowshopping ◴[] No.45342422[source]
That's actually kinda hard, no?

Say the server has a counter. When you load the page, it's at 57, so it displays that you would be ordering #57. While you're looking at this, someone else loads the page - what number do you show them? If you show 57, then whoever orders first gets it and the other person gets a message "Sorry, not available. Want 58 instead?" but the same thing could then happen to them with #58, too – "Sorry, not available. Want 59 instead?"

So maybe instead you show the 2nd person counter+1, i.e. 58. And you show the 3rd person counter+2, i.e. 59. But what if #59 purchases but 57 and 58 don't? What do you show the NEXT person, 57 or 60?

I'm not saying it's intractable but it merits thought.

replies(4): >>45342445 #>>45342451 #>>45342489 #>>45364937 #
cloudmanager ◴[] No.45342489[source]
Exactly why we kept it simple. You find out your number when it ships.
replies(1): >>45342720 #
1. defrost ◴[] No.45342720[source]
What guarantee is there against transit hash collisions?

When two rocks are ordered, several rocks arrive, some with no ID numbers, others with IDs that match previously issued rocks?