A couple of clarifications:

Cold Fusion has interfaces for cgi as well as NSAPI, ISAPI, and WSAPI
so depending upon your web server, you can set it up for the optimum
performance.

CF has multiple methods of "simulating state", and has the ability to
store information on the CF App Server system regarding a particular
session instead of sending all of it back to the clients browser.  When
you have a lot of information that needs to be maintained, this can
certainly speed up your transactions as you are not forced to continually
send/receive that information between the client and the server.  Multiple
methods of storing that information also exist so you can pick what's best
for your particular situation.  By default, it tries to set a couple of
cookies to uniquely identify one session from the next, but you can (as
has already been mentioned) pass them as URL variables, or form fields if
cookies are not being accepted by the client.  This is how I coded the
www.sambaix.com site.  Is it fool-proof, no, but it does work for most
circumstances.

<plug>

  I've *personally* found that CF is the best way to bring up dynamic
web sites, and works with all of the HP3000 ODBC drivers that I've tried
(Linkway, ODBC/32, and ODBCLink/SE).  We used it last year for the SigImage
ballot BTW :)  The one negative about CF is that it doesn't run natively
on the 3000.  You need to run it on a Windows 95/98/NT, Solaris, or HP-UX
box :(

</plug>

Regards,
Michael L Gueterman
Easy Does It Technologies
Allaire Alliance Partner
email: [log in to unmask]
http://www.editcorp.com
voice: (888) 858-EDIT -or- (509) 943-5108
fax:   (509) 946-1170
--

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Evan Vaala
> Sent: Thursday, January 07, 1999 9:07 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Stateless HTTP and CGI on the HP3000
>
<snip>
>
> I believe other packages, such as Cold Fusion may support the
> above mentioned process, but Cold Fusion is cgi based.
>
> Evan Vaala
>