> > If you're expecting to find a CF-based chat program which
> > doesn't rely on automatic page refreshes, don't hold your
> > breath! That's outside the scope of what CF, or any other
> > web application server for that matter, can do.
>
> That's not entirely true.
...
> You could always write a script that keeps serving a page and
> never tells the browser that it is done so the browser keeps
> loading it while content is being added by the script. I know
> this can't be done using cf since the cf engine processes the
> entire script until it's done before handing it over to web
> server for serving, but any jsp engine, or even asp, could do
> this.
Yikes!
Well, you're certainly right about that; you can do that in ASP and other
environments. I'm kind of glad you can't do that in CF, though, and here's
why.
CF, when you start it up, creates a set of threads, and when it receives
requests, it sends each request to a thread for processing. It never creates
new threads, so if you did this with CF, you'd only be able to support as
many users as you had threads for. The number of threads you'd have is set
in the CF Administrator under "Number of simultaneous requests". Now, I seem
to recall that Perl, used as a CGI program, spawns a new thread for each
request, but I don't know if Perl does that when run as an ISAPI module, and
I don't think ASP spawns a new thread for each request either.
So, in short, you'd want to be really careful with this, unless you're sure
you can generate new threads for each request, or you're never going to have
to support more than five or six users at a time on a single web server.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
