[hunchentoot-devel] Hunchentoot with ECL
Edi Weitz
edi at agharta.de
Fri Mar 21 22:33:59 UTC 2008
On Fri, 21 Mar 2008 00:25:40 +0100, css <css at swissjabber.ch> wrote:
> As I noticed, Hunchentoot is not yet ported to ECL, even though the
> ECL-documentation says that it has Gray-Streams-, Thread- and
> Socket-Support as far as I read.
>
> Was there simply no interest to port it to ECL so far, or is there
> any reason why it is not possible or very hard to port it to ECL, or
> why one should not use ECL?
I suppose there was simply no interest so far. You're welcome to
provide patches for ECL.
http://weitz.de/patches.html
> Another thing I am interested in is, why doesnt Hunchentoot use
> "external" Libraries, or store the whole Stuff in the port-*-Files
> in seperate "Libraries" - the functions defined there may be useful
> to other Projects, too, and they would also benefit from bugfixes
> and extensions (and would maybe add such, too).
There already exist compatibility libraries for things like MP and
sockets which I think provide more functionality than what is in the
port-xxx.lisp files. However, they're pretty big and using them would
add another layer of complexity to Hunchentoot which already depends
on a dozen other libs.
Right now there are only a few lines per implementation which cover a
small subset of four implementation-specific areas, namely MP,
sockets, debugging, and OS integration. Loading four external
libraries to cover this seems overdone to me.
Having said that, a lot of the "design decisions" of Hunchentoot might
actually be accidents or workarounds owed to its history - see the
website. If I would start from scratch today, I would probably do a
lot of things differently. But that's not going to happen anytime
soon... :)
More information about the Tbnl-devel
mailing list