News and commentary from the cross-platform scripting community.
|
||
|
Mail Starting 3/10/98 | |
Does Betty have a theme song yet?
From: panicboy@ix.netcom.com (Andrew Sasaki);
Sent at Tue, 10 Mar 1998 15:10:40 -0500;
Theme song?This Betty stuff is wonderful.
From: abbaer@landsend.com (Alan Baer);
Sent at Tue, 10 Mar 1998 11:44:21 +0000;
BettyI know you're moving fast and just getting stuff out here, but you should ship bettyParts with sample responders that work with something other than path. I wondered if it would work with user-agent or IP address, so I fished around, and it does!
That's pretty remarkable because it shouldn't be hard to use the wsf stuff to renderer content through different templates depending on browser type or location of client. Or else to serve static content that's been rendered through different templates. Tremendous possibilities, obviously. And as usual, achievable with remarkable little effort on the users part. As you can see, I'm just starting to grasp where you're going ...
Or is it that you're saving this for the DHTML stuff you've been hinting about?
"Can Betty render 500 pages a minute?"
From: cshotton@biap.com (Chuck Shotton);
Sent at Tue, 10 Mar 1998 09:09:08 -0800;
Re:Bonk!The short answer is probably "yes". I benchmarked the original inetd.http server in Frontier 5, running on my Pentium Pro 200 box, at about 17 connections/second. And that wasn't maxing it out, either.
Add some overhead for rendering and it probably still squeaks in at around 8 to 10 per second. Well within the 500 pages/minute limit.
