[http://naviserver.sourceforge.net/ns_logobig.gif] http://bitbucket.org/naviserver/naviserver/%|%Source Code %|% ✸ http://sourceforge.net/project/showfiles.php?group_id=130646%|%Downloads %|% ✸ http://naviserver.sourceforge.net/n/toc.html%|%API Documentation %|% ✸ http://sourceforge.net/mail/?group_id=130646%|%Mailing Lists%|% ✸ http://sourceforge.net/tracker/?group_id=130646&atid=719006%|%Bugs %|% ✸ https://www.ohloh.net/p/naviserver/contributors%|%Developers %|% ---- **What you should be aware of** ***There's TCL, do I need something else?*** TCL and NaviServer let you solve almost every requirement fast, reliable and straightforward. This is one reason (not the only one) the field of integration with other (scripting) languages is sometimes a little bit untouched. Of course there are good reasons for a native integration beyond the limitations of the Common Gateway Interface. Take a look at the pages of this section to verify the current status of integration. (Note: For now you may have to ask the Mailing List as this summary/documentation is at the early stages) ***Stacksize*** Apart from the specific details of integration of your favoured language you may have to take a look at the stacksize parameter of your config file. As a rule of thumb the default stacksize (in bytes) # # Thread library (nsthread) parameters # ns_section "ns/threads" ns_param stacksize [expr 64*1024] ;# Per-thread stack size. is almost always not enough. Use multiples of 1024 and increase to 1 Megabyte for the start: # # Thread library (nsthread) parameters # ns_section "ns/threads" ns_param stacksize [expr 1024*1024] ;# Per-thread stack size. If the size of the stack is not enough you may encounter crashes without real explanation. ---- !!!!!! %| [Category NaviServer] |% !!!!!!