The strategy of building an EJB client out of a Java applet which uses
RMI to communicate directly with an EJB server is (IMHO) technically
elegant, but not very popular. I am wondering if people have tried it
with jBoss with success and with stories to tell? This is in a
Joe-Public-Internet-User scenario.
We don't need to rehash the standard "firewall issues" with RMI; I think
those issues are pretty well established.
What I'm more concerned with are questions like:
1. What's the footprint of the client files needed? Is there a .Jar file
within jBoss specifically meant for clients? Is it too big that the
average public Internet user would get annoyed downloading it?
2. Does it function well on various Java-enabled browsers, such as
different versions of MSIE, Netscape, Mozilla, etc?
3. What if the client's browser's JDK is 1.2, but my jBoss server's JDK
is 1.3? Any issues there?
4. Is this just a bad idea in general, and should a rich-client applet
be communicating via HTTP and a Servlet (and perhaps XML or SOAP), as
opposed to RMI directly?
Opinions appreciated,
Bryan
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
