Re: passing user info on each page
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 30029
interpreted = N
texte = Howard and Serban, thank you for your replies.My concern with doing a 'quick search' on each page is that most of the current pages these folks are viewing already do a search. The 'users' database would be around 10,000 users initially and grow from there.Although I do like the cookie-less part of that
Maybe instead of doing a [search], create a temp database with a session ID, user level (pulled from the main database initially) and time/date stamp, then simply do a [lookup] on the unique session ID to pull the level. Then have a trigger to clean up this temp database every few hours?The expected traffic of this site (once re-designed) will be around 250,000 pages per day (I hope). So I want to try to avoid any searches that I can. Hence the reason for saving more of the common data into a text file to be used as an include.ThanksDale-- Dale Therio +49 69 263 19977 office Dresdner Kleinwort Benson Research +49 69 263 11379 fax Jürgen-Ponto-Platz 1 +49 170 934 3610 mobile 60301 Frankfurt, Germany > From: Howard Wolosky > Reply-To: (WebCatalog Talk) > Date: Wed, 5 Apr 2000 06:14:18 (EDT) > To: (WebCatalog Talk) > Subject: Re: passing user info on each page > > I prefer to have a members database that has their username, passsword, > and userlevel. Then, have them login using [authenticate]. You'll then > be able to access their entered username and password with [username] and > [password] throughout the rest of their session (until they close their > browser). Then, on each page, do a quick search on the username and > password in your members.db to return the user level. > sha-bang. all done. no cookies, no mess. > > > -Howard > > On Wed, 5 Apr 2000, dale@gmr.dresdner.net wrote: > >> Hello, >> >> I am working on an update to an existing site. The new site will require >> users to log in for most functions. >> >> Based on who the user is, their menus will be different. e.g. beta testers, >> editors, regular users. >> >> As there will be (currently) only about 5 classes of users, and the menus >> will be fairly stable, I will plan on saving the menus out as an include >> file. That will save a it to the database for each page. >> >> The question is, what is the best way to identify the user on each page once >> they have logged in? A temporary cookie, with say just a time stamp and >> their user level? I prefer not to pass a [cart] on each page as many of the >> pages are designed to be bookmarked and I prefer to not clutter up the URL >> any more than I have to. >> >> Thanks for any suggestions. The new version of this site will be even busier >> than the current one. Also eventually there will be a store online (which >> will not require logging in) so at that point I will need to pass the cart >> value. >> >> -- >> Dale Therio >> +49 69 263 19977 office Dresdner Kleinwort Benson Research >> +49 69 263 11379 fax Jürgen-Ponto-Platz 1 >> +49 170 934 3610 mobile 60301 Frankfurt, Germany >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
Howard and Serban, thank you for your replies.My concern with doing a 'quick search' on each page is that most of the current pages these folks are viewing already do a search. The 'users' database would be around 10,000 users initially and grow from there.Although I do like the cookie-less part of that Maybe instead of doing a [search], create a temp database with a session ID, user level (pulled from the main database initially) and time/date stamp, then simply do a [lookup] on the unique session ID to pull the level. Then have a trigger to clean up this temp database every few hours?The expected traffic of this site (once re-designed) will be around 250,000 pages per day (I hope). So I want to try to avoid any searches that I can. Hence the reason for saving more of the common data into a text file to be used as an include.ThanksDale-- Dale Therio +49 69 263 19977 office Dresdner Kleinwort Benson Research +49 69 263 11379 fax Jürgen-Ponto-Platz 1 +49 170 934 3610 mobile 60301 Frankfurt, Germany > From: Howard Wolosky > Reply-To: (WebCatalog Talk) > Date: Wed, 5 Apr 2000 06:14:18 (EDT) > To: (WebCatalog Talk) > Subject: Re: passing user info on each page > > I prefer to have a members database that has their username, passsword, > and userlevel. Then, have them login using [authenticate]. You'll then > be able to access their entered username and password with [username] and > [password] throughout the rest of their session (until they close their > browser). Then, on each page, do a quick search on the username and > password in your members.db to return the user level. > sha-bang. all done. no cookies, no mess. > > > -Howard > > On Wed, 5 Apr 2000, dale@gmr.dresdner.net wrote: > >> Hello, >> >> I am working on an update to an existing site. The new site will require >> users to log in for most functions. >> >> Based on who the user is, their menus will be different. e.g. beta testers, >> editors, regular users. >> >> As there will be (currently) only about 5 classes of users, and the menus >> will be fairly stable, I will plan on saving the menus out as an include >> file. That will save a it to the database for each page. >> >> The question is, what is the best way to identify the user on each page once >> they have logged in? A temporary cookie, with say just a time stamp and >> their user level? I prefer not to pass a [cart] on each page as many of the >> pages are designed to be bookmarked and I prefer to not clutter up the URL >> any more than I have to. >> >> Thanks for any suggestions. The new version of this site will be even busier >> than the current one. Also eventually there will be a store online (which >> will not require logging in) so at that point I will need to pass the cart >> value. >> >> -- >> Dale Therio >> +49 69 263 19977 office Dresdner Kleinwort Benson Research >> +49 69 263 11379 fax Jürgen-Ponto-Platz 1 >> +49 170 934 3610 mobile 60301 Frankfurt, Germany >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
dale@gmr.dresdner.net
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Sku numbers (1997)
WebCommerce: Folder organization ? (1997)
Data Variables partially show up (1998)
WebDNA & Linux RH ES install question (2004)
Locking up with WebCatalog... (1997)
Problems appending to database (1997)
Review comparison by PC Magazine: Open for On-line Business (1997)
REALLY need a hand (1999)
WebCat (or other) Indexing (1999)
restarting service remotely on NT (1997)
Newbie Question about a Logical AND in a show if statement.... (1999)
WCS Newbie question (1997)
[WebDNA] Funding for a new v7+ commerce system? (2011)
[WebDNA] Serial numbers and pricing for WebDNA 7.0 (2011)
Announcement-WebCatalog 2.0 Released (1997)
Help formatting search results w/ table (1997)
Three Guesses? (2004)
Triggers (2003)
CSV import suggestions (2007)
Webstar 4.2 Stops Serving (2000)