Sign In Sign-Up

Welcome!

Close

Would you like to make this site your homepage? It's fast and easy...

Yes, Please make this my home page!

No Thanks

  Don't show this to me again.

Close

EasyThings Web Server ™ version 0.0.5

Special edition (with JSP engine)

New features

We are finally supporting Java Server Pages! This version of EasyThings Web Server is fully complient with JSP specification version 1.0.1 plus some features of JSP 1.1 Public Release 2 are implemented.

We are proud we did it before 19th century is over. We still hope to get feedback from you in this century!..

We also fixed minor bugs in HTML parser plus API now includes JSP parser.

JSP engine (JSPServlet) needs a folder specified in http.properties for storing temporary data. It recompiles JSP page only if page was changed after last regeneration. For your convinience, this version of JSP engine doesn't remove temporary files, so you will be able to see what exactly engine generates for your JSP pages.

Note: this version of EasyThings Web Server requires Java Server Web Development Kit 1.0.1 or later.

Limitations

This version of JSP engine uses <OBJECT> elements in HTML output for representing <jsp:plugin> elements in JSP. It means, such pages may not be properly rendered by Netscape browsers, as they do not support this tag. Future version of JSP engine probably will be smarter end will be able generate different content for different user agents, for example instead of <OBJECT> tag it may use <EMBED> tag. The problem is that when same page is requested by different agents, it may have to be regenerated to provide user agent-compatible output. JSP specification doesn't specify how this situation should be handled, and we hope to your feedback on this issue.

Another limitation is that when JSP page uses <jsp:include> or <jsp:forward> elements in its body, engine will not recompile the page if included/targeted resource is changed. The reason is just because JSP engine has no knowledge about it. One of solutions that my be used is generation of dependency tree for included resources referenced in JSP page. This may also help to prevent recursive includes (which, probably, is not necessary, and, instead, can be a feature: for example, a JSP page includes other resource(s) recursively until, say, an expression returns false).

Yours,
EasyThings Group
12/17/1999