Do we absolutely have proof that the original problem is caused for
sure by session key collisions? The assertion here is that we're
generating 10000 md5s and that NONE of those is unique and so the
function is timing out.
This is preposterous.
If this were actually the case, I could generate my own 10,000 md5s
The alternative explanation is that the cache backend is timing out.
Additionally, UUID4's are only very probably unique. You are proposing
I predict that a patch which removes the 10k loop will make the
Sorry to be blunt, but lets tackle the real problem here, rather than
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.