3 ms·
There’s a difference between using “natural data” and using a “client generated identifier”. This thread is talking about natural data and the example given amo
by dcow 5y ago
There’s a difference between using “natural data” and using a “client generated identifier”. This thread is talking about natural data and the example given amounts to a fussy customer rather than an actual technical problem (not that they don’t exist) with using natural data. Client generated UUIDs are totally fine provided you validate the ID and authorize resource access normally e.g. client A can’t put a resource by UUID owned by client B just by knowing the UUID. Using natural data or not really seems to be a product problem and in the face of inexperienced product managers or changing requirements probably best avoided for the reasons given. It’s not clear which issue the article is addressing, specifically, though.
- bob1029 5y ago> the example given amounts to a fussy customer Just so we are clear, the customer pays our salaries. Client-issued UUIDs seem fine in theory but then start to impose haunting dread when you consider the total space of all possible client devices, operating systems and browsers. At least some of those scenarios are going to have shitty rng implementation or use the wrong type of UUID. At least one of those problematic scenarios will have multiple concurrent users. What do you reach for when your client-controlled supposedly un-collideable identities begin colliding? Why even take the chance?
- dcow 5y agoHTTP 400 and 409