gangstah
msg:947954 | 6:51 pm on Jul 30, 2003 (gmt 0) |
I think I would probably go with the DB route also. I guess that all depends on how much strain the db is already under from page hits and record requests.
|
smokin
msg:947955 | 6:58 pm on Jul 30, 2003 (gmt 0) |
IMO you should limit the number of connections made to an access db, so I would use cookies
|
topr8
msg:947956 | 8:19 pm on Jul 30, 2003 (gmt 0) |
thanks ... more unsure now!
|
smokin
msg:947957 | 8:26 pm on Jul 30, 2003 (gmt 0) |
sorry didn't mean to confuse you, just offering you my opinion ;o)
|
gangstah
msg:947958 | 9:55 pm on Jul 31, 2003 (gmt 0) |
The more I think about, the more I think smokin is right. Access is so bad for Web databases, the fewer hits the better. Go with the cookie.
|
aspdaddy
msg:947959 | 7:53 pm on Aug 1, 2003 (gmt 0) |
Are we talking about dynamic breadcrumbs? This keeps track of the last 3 pages. sub add_to_recent()
session("page3")= session("page2")
session("page2")= session("page1")
session("page1") = request.ServerVariables("URL")
end sub
|
cococure
msg:947960 | 10:44 pm on Aug 3, 2003 (gmt 0) |
I would use aspdaddy's subroutine and augment it with code to get rid of duplicates as well.
|
TheDave
msg:947961 | 7:49 am on Aug 4, 2003 (gmt 0) |
Nice idea actually :) A thought I had was if the product id is stored in a querystring, you could just use a "productX" cookie and set it to the product id, rather than the URL. That way you can request the cookie and grab the product straight from the db. :) Access is evil but I still use it :P
|
|
