gavino wrote:
> On Aug 19, 12:48 am, Bernd Paysan wrote:
>> gavino wrote:
>>> 10,000 YEAH BABY! but in its defense php was talking to db etc with
>>> each apache child....this 10k would be static right?
>> The 10k are static. So when you talk to a database, you have to count how
>> much memory the db takes per client, and what percentage of time the web
>> serves would be talking to the db. You probably could write the performance
>> critical parts of the db as a small Forth program, to reduce that load.
>> Also, the dynamic content part is yet not optimized to keep the connection
>> alive, this costs more Gforth starts.
>>
>> --
>> Bernd Paysan
>> "If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
>
> once I finish starting forth and thinking forth should I know enough
> to read the code of your webserver.....or are there things I need to
> learn elsewhere to do that?
Starting Forth and Thinking Forth are both pretty dated. Some of the
worst problems with SF are fixed in the version posted at
www.forth.com,
but many anachronisms (especially assumptions about how implementations
are structured) remain.
My books (Forth Application Techniques and Forth Programmer's Handbook)
both represent modern systems and usage, and also go into a lot more
detail. There is also a new book at MPE's web site.
But to really get a feel for things, it would help to read the simpler
examples that come with any of the mainstream Forths, and then write
some code on your own. Trying to dive in by reading code for something
as complex as a web server (even a simple web server) is like trying to
jump onto a moving train. Learn to walk before trying to run.
Cheers,
Elizabeth
--
==================================================
Elizabeth D. Rather (US & Canada) 800-55-FORTH
FORTH Inc. +1 310.999.6784
5959 West Century Blvd. Suite 700
Los Angeles, CA 90045
http://www.forth.com
"Forth-based products and Services for real-time
applications since 1973."
==================================================
