>Number: 2906 >Category: general >Synopsis: Propose that Apache recommend $UNIQUE_ID for all "session id" >algorithms >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Wed Aug 26 10:50:00 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: future >Environment: NA. >Description: Many modules (mod_session, mod_jserv, etc.) create their own unique session_id number. They all have limitations that UNIQUE_ID seems to have fixed. I propose these modules be changed to use UNIQUE_ID.
I also propose that Apache module programming documentation be changed to recommend using UNIQUE_ID as well. Having a standard will make things much easier for module programmers. A function to "uu-decode" the string should also be incorporated so the modules can access the exact time of it. (I have a non-system-independent version available). Another alternative is to set an env variable to the time the unique id was made (UNIQ_START_TIME). If everything will be using UNIQUE_ID, the variable should be calculated in the Apache core. >How-To-Repeat: NA. >Fix: NA. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
