This is becomming totally off-topic, and I am a bad, bad person for continuing it. But I feel that deep-down need to respond, so I'm going to burn some karma...
franzR wrote: > > Swing and performance: It seems that Sun pushes its resources to the > server-side because Swing based application eat still a lot of resources and > the performance cannot be compared with native applications like Motif or > Windows. > Evidently this isn't so true anymore. I say this based on demos I've seen recently (on a fast Windows machine, YMMV, etc) > There are several things which cannot be changed (i.e. stack > architecture of Java, interpreting byte code), > Most modern JVM's compile to native code. > To speed up the application I only can recommend to use the thread > technology which is > For what? Unless you're on a multi-processor machine, threads actually slow things down. Gratuitously adding threads is guaranteed to be a bad thing. There's some hope that particular kinds of user-perceived performance bottlenecks can be helped by client-side threading, but there's no particular reason to believe that it would help here. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com ___________________________________________________________________________ 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
