Justin Erenkrantz wrote:
Store that key in the apr_socket_data? Another cheesy idea may be to
use a linked list with the key in the structure. I'm just really
thinking that for the general case, a key/value backing (like a hash) is
overkill. I'm just not clear this is going to be more than 2 or 3
elements at most...
Jeff's proposal is no more heavyweight than what we had before and I
think we definitely should support more than 1 element so I'm +1
for the patch (of course I'm not against any optimizations should anyone
be inclined to code them :)
Allan