There is actually the question that has been bugging me all day today, and is in the subject.
How to debug an weblocks app? The web backtrace from my point of view is a bit terse. I've tried to trace the functions that the backtrace reported errors in, but all I would get was "closure XY has been called" message. I've tried to step my weblocks app, but all I would get is an output of the call to the weblocks app wrapped into call to step. What would be the way to step through the weblocks app using sbcl resources? Also, one more question. As far as I was able to understand from the available documentation, when the weblocks is started, each browser connection creates an thread with the weblocks app and the hunchentoot backend? At what point in the weblocks app this threading begins? I'd like to make an app that has the web part, but also an "daemon" part that listens on an port, and communicates to the web part, but it wouldn't be nice if everything goes to an thread when an connection is made. On the other hand, I'd like to start the "daemon" part when the weblocks app is started. (defun start-sem (&rest args) "Starts the application by calling 'start-weblocks' with appropriate arguments." ; my guess is that the best place to put my stuff that I want to start with my weblocks app is here (apply #'start-weblocks args) ; and a little less but still ok place here (start-webapp 'sem)) -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
