On Tue, Jan 22, 2002 at 02:19:59PM -0500, Gianni Johansson wrote: > Tavin has done almost all of the work you would need to do this already with > his MultipleHttpServletContainer.java. > The piece that's missing is a way to enumerate relevant data (Human readable > text for servlet name, URL ) for other servlet's in the MHSC, perferrably in > the same order they were defined in the config file.
I am really starting to wonder whether all of this servlet stuff belongs in the main config file, it seems like it is more configurable than anyone could possibly wish for. > If the MHSC made this data available through the Servlet attribute mechanism, > then it would be trivial to write an index servlet which listed all the > servlets available on the port and gave links to them. The index servlet > would then just be one more servlet in the MHSC. This solution would be > generic -- it could work for any kind of servlets you want to aggregate on a > port, not just ones written to report status. A generic solution would definitely be preferable. > I think we want to keep status on separate port from fproxy. Most status > servlets need access to the Node reference. fproxy should be able to run > externally from the Nodes JVM. Can't we have multiple servlets on the same port now? Ian. -- Ian Clarke ian at freenetproject.org Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020122/50c6ca54/attachment.pgp>
