[bknr-devel] BKNR web, best place to start digging

Frederico Muñoz fsmunoz at gmail.com
Fri Jun 4 13:21:06 UTC 2010


Hi Hans,

Thank you for both the quick reply and going through the effort of
changing the code; without I would not easily understand how to
proceed, even because the hunchentoot documentation omits that
option... had I read the class documentation I would likely have found
it out...eventually.

2010/6/4 Hans Hübner <hans.huebner at gmail.com>:
> I pushed a fix to the :HELLO-WEB project that removes the problem that
> you report.  The issue is that one needs to specify a
> :REQUEST-DISPATCHER argument when creating the Hunchentoot ACCEPTOR
> object in order to switch off Hunchentoots internal dispatching
> mechanism.

Exactly, I understand it now.

> I have a patch for Hunchentoot in the works that will remove all of
> the callback arguments and replace them by generic functions.  Then,
> BKNR will have a BKNR-ACCEPTOR mixin class that one has to use and
> that implements the required protocol callbacks.

Right, I (sort of) see.

> But for now, you
> should be good to go with your experiments.  I'll fix the Quickhoney
> project as well, but HELLO-WEB is a better starting point for
> something new.  You can always look at the other projects for
> reference.

I'm looking at the projects, but the way I tend to learn is by
starting small and doing it myself, otherwise I get lost very quickly;
in this case I can't really understand what is going on (and thus
benefit from what is already written) without at least understanding
the basics and being able to make something as simple as something
that prints "Hello world". Since now I can already do that it is
easier to pick code from the projects and understand what they do.

The hello-web project is now working, as is my own small experiment.

Best regards,

Frederico

PS: Actually I still have a small issue, but this one will be easier
for myself to fix: I get "URI scheme :HTTP not supported" errors on
the index, which Is likely tied with cxml not loading http DTDs. This
is probably something related to the template mechanism.




More information about the Bknr-devel mailing list