Re: HTML
Richard Maher wrote:
"Arne Vajh?j" <arne@vajhoej.dk> wrote in message
news:49dbff1e$0$90276$14726298@news.sunsite.dk...
Richard Maher wrote:
I got the example from a SUN page not dissimilar to his one:
http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/using_tags.html
Maybe you should let SUN have a compy of your code as well?
Not all of SUN's docs are equally good.
Java applets has been [USED TO BE] a low priority for many years. I would not
be surprised if very few resources has been applied to applets docs.
Sorry to reply twice to the same post, and let me acknowledge up-front that
you and Andrew could well have forgotten more about Java than I currently
know. But as a casual observer, if nothing else, I can't let the old wife's
tale of "SUN deprecating Applets" go by unchallenged again.
It is simply unfathomable that SUN would invest the substantial time and
dollars to completely re-engineer the JRE with separate threads to support
concurrent multi-version JVMs, if it was a technology on the wane. Java 6
was a watershed, a Rubicon, a something else big, in the direction of Applet
development!
What about policy files for cross-domain Socket (and presumablt
httpConnection) access? What about JNLP-esque deployment of Applets? More
new features for yesterday's technology? Just because JAVA as a web GUI may
be suffering (perhaps deservedly so) does not mean the Applet is doomed.
Adobe and Microsoft will be playing catch-up for years with the
functionality that the JAVA launch-pad has provided for years. (Just have a
look at Sockets in Flex and Silverlight to see what I mean)
Some things has happen recently with applets. Java 6 Update 10 actually
added some stuff.
Most likely inspired by Silverlight and the "so ein ding mussen wir
auch haben" mentality.
But from Java 1.2 to 1.6 not much did happen.
Maybe JavaFX and the push for RIA can keep applet development
moving.
We will see.
PS. Is it really true that JAVA doesn't get asynch i/o functionality till
Java 7? Cutting-edge stuff - Maybe it's the server side that's dragging.
Java has had non-blocking IO since NIO was introduced in 1.4.2 - Java 7
will maybe (I don't follow what is in and what is out that careful)
contain NIO2 which contains the so called Asynch API, which from a quick
glance look as a smart way to manage threads on top of the original
non-blocking IO.
It is probably also a catch up thing, because .NET has such things. But
if someone need it, then they should be able to code the necessary stuff
today on top of NIO.
Arne