httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "R.J. Kraaij" <terdu...@worldonline.nl>
Subject The Wun (worldwidewebuniquenumber)
Date Fri, 02 Apr 1999 09:13:06 GMT
I'm working a Server Side Client Identification, a method, to recognize a
client during his session, a method capable of Differing Clients on the
Server, even if they'coming along of the Same proxy.

I'f seen two different Modules of this on the Net :

1) They place a identifier in the Left behind the host :

  http://somehost:someport/1234-5678-9ABCD/index.html

2) They place the method at the end of the URl :

  http://somehost:someport/index.html/1234-5678-9ABCD


Now, Using Referer technology (which is enabled by far more users then
cookies) one should be capable of tracking a user, Server Side..

This ,combined with the Shared Memory Pool enables "Real Client Pools" 
and gives a webmaster a real idea about how many diferent users are on
his(her's) System.

When Plotting this out, i came to some questions


1) How long should a WordWideWebUniqueNumber be (WUN) ? 
2) Where inside the Apache Architecture could a WUN be placed eg, to
   which struct do we at it..
3) the functions like " ap_get_wun(..), ap_check_wun, ap_create_wwun
   are they best placed inside a new file, or stick together in the
   archecture.


the basic idea why i came on this one, is that 'f been using get request
for a while now, to overcome problems, with schools, who use my
chatsystem, but have browser, which a forced no cookies allowed.

it's okay to use get's for that, but i think the architecture will be a
lot easier when i knock it off with wun's.

And wun's also could be used, to create pools, wich could be accessible
only by some wun's.


any idea's, tips, or Twappings would be nice :o)

		*waves*
				- Reinder Kraaij







Mime
View raw message