Servlet runs server-side and thus requires large overhead and configuration on the server's end and the HTML is actually output in streams
JSP runs (I believe) client-side and is usually used when only a small amount of data needs to be generated via Java code, since the page is just HTML with Java snipets inserted.
--Greg H
On 11/5/05, Lynn Allan <[EMAIL PROTECTED]> wrote:
I might be able to help out with jsp pages ... it has been several
years since I worked with java servlets and tomcat, and I recall it
involved LOTS of things to get "knitted together" correctly so that
pages show up ... and the "chain of events" can take some getting used
to ...
My impression is that with a tutorial on how to get a localhost set up
for something like apache tomcat, the actual generation of content
pages isn't too bad ... but there was definitely a learning curve ...
for me at least
http://www.apl.jhu.edu/~hall/java/Servlet-Tutorial/
Seems like some existing crosswire pages could serve as templates,
perhaps in a "sandbox" scenario???
*********************************
Another thing to bear in mind is the infrastructure of the technology
powering the Web site. There will not be any changes to the
infrastructure at this time. For now, we need to stick to using
technologies like Apache/Java/JSP for the content rendering, as such
as used currently. The firebird database engine is also available. As
Greg H. mentioned, within reason. So, part of "reason" includes those
technologies. (I asked what was available and this is the list given
to us.)
God Bless you all!!!
In Christ,
Greg M.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
