I believe I've managed to sort out all the issues we found in the chat room today. Talk about a trial by fire. :) But it's all good and stable now. I sat around for several hours chatting with a half-dozen other folks without any noticeable problems, and I don't think it was keeping anyone out.
What I decided to do in the end is to leave the decision basically up to whomever is running the site. The chat room now has a uniqueid attribute which allows you to feed it whatever you use to uniquely identify the client or user. The user may still enter the chat room more than once ( with different nicks ) or enter multiple rooms if you allow them. Due to continuing problems with cookies the uniqueid attribute however defaults to #CreateUUID()# which is generated on the form page and then passed to the entry page where the talkontap.swf interface is displayed... If you're using the chat room in a logged-in area, you can feed your unique user id string ( whatever it happens to be ) to the chat room as the uniqueid attribute and the chat room will use that to determine if a given nick is already in use. If your site uses cfid/cftoken pairs, you can pass it as uniqueid="cfid=#cfid#&cftoken=#cftoken#" ... it's all up to you... Isaac www.turnkey.to 954-776-0046 > I'd go for the Cookie option. > Kind Regards - Mike Brunt, CTO > Webapper > http://www.webapper.com > Downey CA Office > 562.243.6255 > AIM - webappermb > "Webapper - Making the NET work" > -----Original Message----- > From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 08, 2002 11:29 AM > To: CF-Talk > Subject: Re: onTap chat room... >> I'm getting an error on the first page and then when I >> "connect" I get >> nothing where the flash portion is supposed to be. >> >> Win2k, NN 6.21 >> >> Hatton > Yep, you probably tried to access it while I was trying to > fix it. :) > Try it again, I modified the <cfapplication> tag ... Make > sure you accept > the cookies <blech> ... I think there may be a way to > avoid the cfid and > cftoken variables all-together although this would require > passing a unique > key as a form or url variable ( since at some point both > client and session > variables are liable to rely on that cfid / cftoken pair > anyhow ) ... I'll > have to muddle with it some more when I get home and see > what I can come up > with... > QUICK POLL: the cfid and cftoken pair in this case are > only used to prevent > nick duplication, i.e. 2 users in different locations > sharing the same name > in the chat. Which is better ( or worse dpov ) passing a > unique key to the > chat entry via url or form variables or requiring cookies? > ... I don't like > either solution, but them's what we gots... > Isaac Dealey > www.turnkey.to > 954-776-0046 > __________________________________________________________ > ____________ > Signup for the Fusion Authority news alert and keep up > with the latest news in ColdFusion and related topics. > http://www.fusionauthority.com/signup.cfm > FAQ: http://www.thenetprofits.co.uk/coldfusion/faq > Archives: > http://www.mail-archive.com/[email protected]/ > Unsubscribe: > http://www.houseoffusion.com/index.cfm?sidebar=lists ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
