tbnl-devel April 2005

tbnl-devel@common-lisp.net

5 participants
13 discussions

[tbnl-devel] A Small Problem with TBNL Stand-alone
by Bob Hutchison 02 Apr '05

02 Apr '05

Hi, I'm back from vacation and am now integrating 0.5.2 into my main code base. This so I can make use of the Araneida and standalone TBNL. It didn't work. I got it to work by changing how *use-modlisp-headers* is used. I've attached a patch. I think you must have changed how I was using it while cleaning up the patch I sent originally. Cheers, Bob ---- Bob Hutchison -- blogs at <http://www.recursive.ca/hutch/> Recursive Design Inc. -- <http://www.recursive.ca/>

2 5

[tbnl-devel] basic package question
by Jason Wang 02 Apr '05

02 Apr '05

hi, i have read through the documentation for both TBNL and CL-WHO, i have created a page based on what i read.. but i found out i can't figure out how to test the page.. i can see the test page by doing (asdf:oos 'asdf:load-op :tbnl-test), how do i change package from :tbnl-test to something else? what code do i need to add? i have tried just adding a folder and declare (in-package #:tbnl-test2), that didn't work out too well.. what do i need to do in order to start test2? thanks alot :D ps. if this is on the documentation, please excuse my ignorance.. i indeed have read all of it and didn't find any answers to it.. -- www.programer.name - my own personal blog : )

2 3

[tbnl-devel] That Memory Consumption Problem Unique to OS/X (Again)
by Bob Hutchison 01 Apr '05

01 Apr '05

Hi, I've been looking into that unbound memory consumption situation when directly connecting to TBNL (that doesn't happen when going through mod_lisp or Araneida and only seems to happen on OS/X). I put some debugging statements into KMRCL and have (finally) noticed something that was blindingly obvious before. There is a KMRCL function lw-worker in listener.lisp that is called for every request made to TBNL directly. It is called only once (or, at least, a very few times) if TBNL is invoked indirectly (i.e. via mod_lisp or Araneida). The call to this function is through a lambda that is defined in make-socket-server and passed to comm:start-up-server. I am assuming at this point that this has something to do with the problem. Now, I don't really understand what is going on here. I will continue to look into this, but if anyone happens to already know what is going on here I'd love to hear about it. Cheers, Bob

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel April 2005