You would be amazed how old all the specs are. These are just what is set to be the standard practice for all webservers to abide by at a minimum so that browsers can communicate with them without custom code changes or handling.
You should see the dates on SMTP and POP3 protocols.
>Wow, that's some old stuff ... Feb 1997!?!?! I think ASP.NET is probably just a little bit different than classic ASP, so I wonder how much of this stuff still applies.
>
>
>
>>There are multiple routes but the standard is this one.
>>
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2109.html>>
>>You can check it our for more information.
>>
>>>I believe that's the same Session object I was referring to also. Anyway, doesn't matter. Just as long as people know that there are a few options out there for managing this stuff.
>>>
>>>~~Bonnie
>>>
>>>
>>>>The session information I am referring to is the Session object for IIS.
>>>>SQL Server may do things differently, as one person suggested URL parameter information.
>>>>
>>>>I don't know exactly how SQL server does. My scope was only with unix and IIS cookie management for server state as referenced in RFC#2109
Brian Seekford
Seekford Solutions, Inc.http://www.SeekfordSolutions.comInternet ActiveX Controls and .NET Class Libraries.
SMTP/S FTP POP3/S HTTP/S SNTP MIME PING WHOIS TRACEROUTE NNTP DNS MX
Base64, UUEncode, yEnc, MD5, SHA1, URL, Quoted-Printable.
Resizer and Tooltips
Email Verification and more. Check us out!