[Jscheme-devel] Version 7.0 and Servlets

[Timothy J. H. <ti...@cs...>]

I ran into a little problem using the new jscheme.jar for servlets. It 
seems that Jetty
creates several threads for handling the servlets and each thread now 
creates its own
interpreter which has its own environment!

Before,  I could just do a define in one servlet and all later servlets 
would have access to the
definition. I may be able to switch back to that model (by using the 
jscheme.JS class instead
of jscheme.JScheme), but its an interesting example of the kind of bugs 
that can arise when
adding new features....

Another fix is to explicitly import any modules that you need when you 
generate a webpage.
Since modules are cached, this won't slow down the servlet engine much 
and it is cleaner
than my old adhoc approach...

 From a development point of view though, this will require the addition 
of a "reload-module"
procedure that disregards the caching when a module is changed.....

---Tim---