3 ms·
> 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 t
by 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