I would be of the opinion that you can have applet/servlet combos that work
well. But I know just as many people who have don't think it's a good idea
than people who do. My company has been tweaking ours for a real long time
and we still have occasional problems with it (Proxy Servers, Really slow
connections, etc.) The servlet side is no problem. If there are problems
it is with the applet making URL connections reliably. If you follow this
route make sure that you use only AWT (Java 1.1) instead of Swing.
Requiring you users to have Sun's JRE/Plugin is most of the time is
unreasonable. Specifically, be ready for users to have problems with
java.io.StreamCorruption exceptions if they are behind services that screen
what URLs they are allowed to visit (or modify headers, etc.) Read Jason
Hunters book "Java Servlet Programming" -- there is a complete example.
Here a link that we used:
http://www.j-nine.com/pubs/applet2servlet/index.htm
James Wilson
Web Developer -- Servlets, EJB, JSP, ASP
Application Developer -- Java, VB
Pocket PC Developer -- eVB, eVC
HealthFirst Corp.
www.healthfirstusa.com
(505) 344-1400 ext 111
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of
> Deshmukh, Abhijit
> Sent: Thursday, October 26, 2000 1:42 PM
> To: [EMAIL PROTECTED]
> Subject: [SERVLET-INTEREST] Applet-Servlet Communication methods
>
>
> I'm pretty much new to the Java world & have written a few
> servlets to write
> back a plain HTML page with tables.
>
> I have read that applets should be used with servlets to write
> professional
> applications as a HTML output is not very presentable ( & tedious too ).
>
> Or is JSP the best choice ?
> Can someone give me some details/resources on this ?
>
> Thanx in advance
>
> Abhi
>
>
>
> This message is for the named person's use only. It may contain
> confidential, proprietary or legally privileged information. No
> confidentiality or privilege is waived or lost by any mistransmission.
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and
> notify the
> sender. You must not, directly or indirectly, use, disclose, distribute,
> print, or copy any part of this message if you are not the intended
> recipient. CREDIT SUISSE GROUP and each of its subsidiaries each reserve
> the right to monitor all e-mail communications through its networks. Any
> views expressed in this message are those of the individual sender, except
> where the message states otherwise and the sender is authorised to state
> them to be the views of any such entity.
> Unless otherwise stated, any pricing information given in this message is
> indicative only, is subject to change and does not constitute an offer to
> deal at any price quoted.
> Any reference to the terms of executed transactions should be treated as
> preliminary only and subject to our formal written confirmation.
>
> __________________________________________________________________
> _________
> 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
>
___________________________________________________________________________
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
