Hi Peter,
On Fri, 16 Apr 1999, Urban Peter wrote:
UP |In fact, we have some code ready. It implements the SSI tags include,
UP |flastmod, config, fsize and echo, and other tags could be added easily.
That's cool - since the development SSI contains several improvements
(cleanup, memory consumption), and the TagHandlers have an easy interface,
transforming them to TagHandlers would be the way to go (IMHO :-)
There is one problem left with the current implementation of JServSSI (1.0
and development) and I didn't find the time to clean it up finally - that
is the reason why the devel-SSI isn't out yet as 1.1. If you could provide
TagHandlers for the abovementioned tags I'll smooth out the last glitches
and we can provide a fully featured JavaSSI soon! I think of a Servlet
with parametrized features (switch on/off Tags <-> TagHandlers)
UP |About the code: the parsing of the tags is rather similar to your
UP |PageParser & *TagHandler stuff. There is one handler class for each SSI
UP |tag. Merging into the development branch would probably just mean adding
UP |TagHandlers for tags like "!--#include" and dumping our own PageParser.
yeah. Seems to be easier to maintain _one_ PageParser than many. The
development efford has to be done once - that's the reason why I designed
the TagHandlers.
So, in one word, I'd appreciate it, if you could convert your work to use
TagHandlers (and feel free to extend the TagHandlers interface, if
needed).
ciao,
-hen
BTW: devel-Branch is jservssi_1_1-DEV
---
Henner Zeller [EMAIL PROTECTED]
PGP pub key [77F75B39]: finger [EMAIL PROTECTED]
"One difference between SuSE and Red Hat is that the former operates in a
country where people don't sue each other over coffee being too hot."
Linus Torvalds
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
