codesite-noreply at google
Sep 8, 2009, 12:16 AM
Post #3 of 10
(717 views)
Permalink
|
|
Issue 550 in cherokee: RFE: mod_unique_id functionality
[In reply to]
|
|
Comment #2 on issue 550 by alobbs: RFE: mod_unique_id functionality
http://code.google.com/p/cherokee/issues/detail?id=550
I'm afraid, we cannot commit this patch upstream because of a number of
reasons:
- Even though it works for simple scenarios, it is quite far of doing what
UNIQUE_ID
does in Apache. For instance, it's supposed to working in a cluster
(different
cluster nodes will not return the same unique_id value).
- The second major problem is the performance. There are architectures/OSes
where the
random number generation is slow as hell. We should not even think of
generating 24
random numbers per request. That'd have a considerable performance impact
in the
server performance.
A better approach could be: (I'm just thinking loud here, I haven't checked
it..):
- Use the connection unique ID
- Use the keep-alive value
- Use some value that would identify the host (the plain text hostname?)
- Mix all those together, (hash it?, ) and generate a 24 chars length
string.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
