Dropping multiple drinks is not handled well.

[bencentra]

I am working remote, but both credit deductions and what actually gets dropped is a mystery when you try two overlapping drops as one user. For example, start one drop at a long delay (10+ seconds) and, in the mean time, dropping another drink immediately. At the very least, this will seemingly only perform the second drop and definitely deduct the credits from the second drop.

I should either:

• Restrict drops to one at a time.
• Set up a drop queue

For now I'm going with restrict to one drop.

[bencentra]

Trying again with the same slot (and not one that is actually empty), the second drop appears to override the first drop. This is because there is only one $scope.current_slot to drop from at a time, and the delay happens client-side so no drop is triggered in the first place.

[bencentra]

Possible solution (with current client-side delay model):

• User drops drink, save all relevant dropping info in new object
• Create a new timeout (don't reuse $scope.dropTimeout) to handle the drop delay
• Queue/save both dink object and timeout
• When one timeout finishes, clear the timeout and the associated drink object

[bencentra]

Switch to server-side drop endpoint means only one drop can (safely) be triggered by the user at a time. However, dropping then closing the page will still perform the drop. Multiple drop calls may result in hardware errors (slot can't initialize if it's already dropping a drink).