This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Re: various kawa check-ins
Per Bothner <per@bothner.com> writes:
> I've recently changed CallContext to be per-thread, using a thread-based
> hash-table. KawaServlet registers the current thread and the
> ServetCall Context in that table. Th next step is to move the
> fluid-binding support from Furure into CallContext, which is an
> easy task, though I haven't done it yet. (It's mainly figuring
> out/remembering how the various pieces fit together.)
>
> One that is done, you'll be able to use fluid-let in servlets, and
> it would be easy to have KawaServlet register the appropriate variables
> in the dynamic state.
That would be very useful. It was my hope that it would be possible.
When it happens will this be portable or will it depend on
KawaServlet?
My eep tool compiles to a single static proc - not to a
KawaServlet. I'd very much like to be able to use fluid-let inside
eep.
Nic