Hello All,

Please disregard the second question. The license on CL-HTTP is not very attractive.

Thanks,

Gerry

Hello Everyone,

I have recently started learning Lisp/LispWorks  and I could use some advice on a couple of things. I have decided that I’m at a point where I probably need to just dive in on a project. The project I’ve chosen has a couple of requirements that I would like to get some advice on in terms of approach. I would very much appreciate hearing the voice(s) of experience on these.

1.       I need to display a group of images in CAPI in much the same way the Adobe Reader displays a pdf file. A collection of image pages that can be scrolled up and down. I have been reading the CAPI docs and realized that this will definitely require a custom widget. I’m wondering how y’all would approach writing something like this with CAPI. I’m not asking for code. I’m just looking for a pointer in the right direction.

2.       My project also needs an embedded web server. I have played with Hunchentoot a little bit and it seems quite capable, but I read a couple of posts where they recommended CL-HTTP and something about threading issues with Hunchentoot. It can be fairly hard to separate fact from fiction and the present from the past on the web. I’m not  being critical of Hunchentoot. I just wondered if there was any reason I should consider using one over the other? It seems that Hunchentoot is considered by many/most to be the first choice, but I figured it wouldn’t hurt to ask. My application will need to handle a reasonably large load at times, so threading/performance issues do matter.

3.       I’ve been reading about the ability to use LispWorks as a DLL/shared library. This seems like an interesting way to deal with the daemon process situation on Linux. Is there any reason or gotchas that would make doing this a bad idea? Does anyone have any horror/success stories they can share?

Thanks for your time,

Gerry