Hacker News Reader

Comment by Boltgolt | Hacker News Reader

IIRC the first envelope scanned at a sorting facility invalidates the postzegelcode immediately, any envelopes using it after that will be handled like they had no postzegel at all (receiver has to pay)

View on HN

What if you mail 2 and they are scanned at the same time and the database isn't up to date yet?

Seems strange they would design a system that could scan faster than they could process the DB, no? I assume there's some queue in between. But the real answer is probably just: multiple scans happen for the same piece of mail. Eventually, one or both of them will be marked as due for payment. The question then becomes, was it worth saving the postage cost for what is potentially a much costlier penalty?

You may find they will refuse service to you for unspecified reasons.

This seems fairly unlikely to ever occur. The database would have to be decentralized, and the two items would have to be mailed from separate locations and both be scanned more or less simultaneously—or within however many minutes it takes for database changes to propagate, which can’t be all that long since you’re able to buy a code and use it on the same day.

Given how remote the probability of this happening is, simply ignoring it and delivering both pieces probably isn’t unreasonable. Or flag it for further investigation and maybe bill the sender or recipient for an additional piece of mail.

And even if for some reason it does occur more often, a message queue is a common, and rather simple solution for this.

Reply on news.ycombinator.com