by Hi,
I know enough about Java adn JDBC, but I don't have a whole lot of
'industry' information,
that is, the standard industry ways of dealing with standard problems. Could
somebody please
make some suggestions for the following scenario:
I'm writing a bean that interacts with a data access bean (which uses JDBC).
The bean works
well in an application setting, but I think in an applet it would have
problems. Not because
of the bean itself, but because of the fact that any applet that used the
bean would need to use
a data access bean.
I understand that JDBC allows for connection even to a remote database, but
the security
aspect of Java applets won't allow (without signing) access to any other
machine accept the
one from which it was downloaded. Having read about JSP, it looks like the
ideal way to
accesss remote data, using a data access servlet. That's fine if you're
happy to use an
HTML form as a front end, but what about my case, where I want to use an
applet (with
my bean in it)? How does an applet communicate with a servlet? Must it be
through
HTTP/XML? This seems wasteful - all that request-forming and reply-decoding
would be very time consuming. RMI seems like a way to avoid this, but here
is my problem:
I don't want to reinvent the wheel. Is there some standard way to establish
non-HTTP comms
between applets and servlets? Can RMI be used in this context?
Apologies for the vague line of questioning but I hope this issue rings a
bell with somebody
out there.
Thanks,
Brendan Lawlor.