One comment that I wanted to make about something you said that was happenning on startup. I think that you said that people were trying to get in before the scheduled time. Why not add an IF action at the beginning of the taf to check the currentdate/time and send the user to an alternate page if it is too early. We recently did this on a sale site that was set to end on January 31st. Once the server hit February 1st, the sale was over and anyone visiting the site got a page stating so.
An idea for next time. Hope this helps, Steve Smith Oakbridge Information Solutions Office: (519) 624-4388 GTA: (416) 606-3885 Fax: (519) 624-3353 Cell: (416) 606-3885 Email: [EMAIL PROTECTED] Web: http://www.oakbridge.ca > -----Original Message----- > From: Dan Stein [mailto:[EMAIL PROTECTED]] > Sent: February 4, 2003 3:39 PM > To: [EMAIL PROTECTED] > Subject: Witango-Talk: Open site "disaster" Summary > > > OK here is what I learned and did. Thanks a lot to Jason who > helped me work > through this. It was money well spent for an extra pair of eyes and a very > reasonable consulting fee. > > 1. I was passing the userreferance arg everywhere that was not an issues > but: > 2. I was doing it a little two much. I was passing it at the > start.tml page > and on the logout results before purging user variables when they > clicked on > start over. The net effect was that was in some cases causing a > "cached" UR > to come up after log out or time out and if the start.tml page was cached > which could easily happen on the client end then a bad UR could be passed. > > The problem was solved with some JavaScript that Ian sent in a > previous post > on this issue but I did not think I needed to implement. > > There is no way to really test the fixes for sure but one can see that > without the UR being based at start.tml and logout ( log back in again) > there is a unique number generated. > > 3. site traffic was busy with almost 100 people logging in during > the 1st 5 > minutes but the server seemed to handle it the garbled UR was on my code. > > 4. There were a few other small bugs that could cause errors under heavy > traffic that Jason spotted in the key tafs we reviewed. > > 5. There was a case where a user could be confused if they added a family > member when they were in course selection because I was not refreshing the > referring window. Jason wrote that code and explained it to me. Thanks to > Jason and for Scott C for the original JS. > > So moral of the story is that second pair of eyes is what is > needed and the > server on Windows at least seems to do what one would expect, > assuming your > code is right. > > Thanks to all who made suggestions and responded to my dilemma. > > Dan > -- > Dan Stein > Digital Software Solutions > 799 Evergreen Circle > Telford PA 18969 > Land: 215-799-0192 > Mobile: 610-256-2843 > Fax 413-410-9682 > FMP, WiTango, EDI,SQL 2000 > [EMAIL PROTECTED] > www.dss-db.com > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
