[Tutor] httpd in your laptop?!? serve web pages and wikis in your notebook?

Luke Paireepinart rabidpoobear at gmail.com
Fri Mar 2 17:40:58 CET 2007


> forth uses a dictionary to locate and execute all its functions and 
> subfunctions. it is a threaded language. so it spends much of it's 
> time looking up functions in the dictionary. in large programs this 
> results in the majority of it's excecutiojn time being spent in the 
> dictionary, and as complexity increases so does dictionary time as a 
> percentage of total time spent on the program- therefore efficency 
> falls as size and complexity rises. while very good for small programs 
> to imbed into controller cpu's to bury inside some machine, when used 
> for a large and very complex application, it falls off in terms of 
> speed and efficency. still, it is a very unusual and powerful 
> language, with a fair sized following. Most progammers find is is SO 
> different that rank beginners learn it faster than experienced hands 
> do. it's just so damn odd.
That sounds really interesting.  I'll have to read up on that after 
class :)
>
>>  From what I can see it's overkill and makes things needlessly 
>> complicated.
>>
> Actually, the server is simple to find and install, saves me the 
> trouble of writing it, and the one I settled on has very light impact 
> and is free. I do have a python server script, but it tends to break 
> at the least exception for some reason, and the reason is not 
> apparent. this program  i found is pretty bullet proof, after i 
> pounded on it to no error or failure, so this also gains a gold star. 
> the python script does not like to be handed mangled links and a few 
> other naughties. as I said, the wiki is still under devlopment, so it 
> sometimes is in a momentary state when it is emitting strange data, 
> and it's a bother to restart the server over and over. while the wiki 
> is now to the point this is not a big problem, it still occasionally 
> happens- i am working on why- and a server that does not break is an 
> assett.
I see your point.
Another advantage for using a Python server, though, is that you can get 
the request objects directly.
So you can, for example, have the query http://yoursite/SomeExampleName and
http://yoursite/SomeSynonymousName actually read from the same source of 
data.
In the non-python solution you'd have to make a new .html file for every 
page you wanted.
Unless I misunderstand how you're using the server.




More information about the Tutor mailing list