>Well, since you guys are writing web applications that target any browser that was ever released and you can't tell the user the site uses cookies, then try passing your variables as querystrings or form variables between sessions.
>
>><< Have you tried using cookies? The cookies would be available from all web
>><< apps. This would eliminate the need for maintaining state with session
>><< variables or session classes.
>>
>>Actually, I'm using them now. But from what I understand doesn't each client browser need to have them turned on in order for me to use them effectively? If so, then this is not an option for me...
>>
>>Thanks,
>>Michael

Actually, I just think in terms of the people who will visit the site. If it's for the general public, you want to draw and keep people in, including the paranoid and security over-conscious who fear cookies like I do the boogeyman (OK, OK, my secret's out...). Plus, you never know if they could be on Lynx, older Netscape or IE, anything. Of course, I'd like to make something dirt cheep and simple, unfortunately, not everyone would be able to use the site.

Actually, I'd like to hear from people who don't allow cookies to be set as to their motives (anyone of you around?) From what I've read regarding cookies, they can only be accessed by the site that created them, so Microsoft can't go in and look at the cookies you have with netscape.com, or even hotmail since it's not the same domain name.

Hugo