Maybe. But what really makes sense is using servlets for
prototyping applications which will then hard-coded using
other lower-level and higher-performance environments (namely
ISAPI...). Servlets are easy to stretch the required
functionality and adjust it, and its true that a lot of
java classes for almost all the tasks you might think of
are avalilable (some king of idea exchange :-) ). You find
and check them and after your prototype is doing what it
should/expected and all the functionality is implemented
in draft you have a sit somewhere with a good case of bear
and rewrite all in C++ or some. Safe and effective.
Do not forget that with simple tools you only get simple
results.
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Tim
> Panton - Westhawk Ltd
> Sent: Saturday, March 18, 2000 1:35 PM
> To: [EMAIL PROTECTED]
> Subject: move to unix (was re: )
>
>
> Using servlets for portability
> absolutly does make sense.
>
> I regularly write servlets on Nt,
> and then deploy on one of the
> many servlet engines.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
