> Java 6 ships with a web server: > com.sun.net.httpserver > > for this, but, again, it's still a lot to take on, given that the needs are > modest. > > > IMO, best to keep the content separate from mechanics... All content files > (HTML/JavaScript) > should be editable using HTML editing tools (TextPad!) and viewable straight > up. >
>>> >>> I have seen struts in action... DON'T DO IT! :) >>> >>> IMO it would be *alot* of work to port, for a negative benefit (it >>> would be bigger, slower to start, slower to run, harder to maintain...). > Bombe's lightweight templating code is quite interesting too. It's >> actually faster than our current code, but it'd be a fair bit of work to >> port it. >> >> We should discuss this some more. I think Ian has some experience in these >> things? >> > httpserver delivered with the Java 6 is only a simple webserver and is not a servlet container. on the other hand I don't think that it would be complicated to imitate some vital functionalities of a servlet container. I was aiming to utilize VelocityView which uses Servlet technology, thus needs a servlet container (and that's where jetty comes into play) Those for MVC architecture say "Ayeeeee" _______________________________________________ Devl mailing list [email protected] http://freenetproject.org/cgi-bin/mailman/listinfo/devl
