Re: Is it bad to connect to a database via an applet?
On May 19, 10:33 pm, Dave Miller <nonregiste...@coldrain.net> wrote:
Andrew Thompson wrote:
On May 19, 12:46 am, Dave Miller <nonregiste...@coldrain.net> wrote:
Andrew Thompson wrote:
But then, it sounds ..vaguely, like you are trying to
convince yourself that it is 'still OK to deploy
applets embedded in web pages'.
It never was, they are a kludgy mix of thin and rich
client, and the deployment situation only gets worse
with time, not better.
It was and is "OK" to use the technology that works best for s
particular situation.
http://www.w3.org/TR/html401/struct/objects.html
What is 'some W3C *recommendation*' of HTML
elements intended to support?
Note that Mozilla based browsers do not even
*recognise* the 'object' element*. To get a
common element supported by browsers to embed
applets, you need to use the (HTML 3.2 based)
<applet> element. (Ignoring that horrid,
unmaintainable, invalid - according to W3C
recommendations - nested object/embed element
hat Sun recommended for far too long).
* There was bizarre circumstance in which I
got one version of a Mozilla browser to recognise
the object element, but only if the element
lacked any versioning information - and then you
may as well use HTML 3.2 and the APPLET** element.
** *Which is just what Sun uses in its deployJava.js.,
after the scirpt has ensured minimum version is
available*
So, what exactly was pointing to the W3C HTML
definition of an object element supposed to
..prove, exactly?
That you know the W3C exists? Hurrah..
OTOH - If you are really wedded to the idea of
embedding applets - don't let me stop you.
On the contrary, you seem to want to deprecate perfectly workable
solutions.
Applets? Live and learn.
If it's the latest and greatest ..
Your the first to mention that. JWS has existed
since Java 1.2.2, BTW.
--
Andrew T.