SUn's Bug Parade did say that Swing on remote X IS slow. The workaround
is not to use double-buffering:
http://developer.java.sun.com/developer/bugParade/bugs/4204845.html
Nathan Meyers wrote:
>
> On Tue, Mar 06, 2001 at 08:35:32AM -0500, Martin, Stephen wrote:
> > This isn't really a Blackdown problem but does relate to Java under Linux.
> > I've been trying to display a Wwing application through X-Windows from one
> > machine to another across an ISDN line. Performace is horrible, it takes a
> > long
> > time to open windows, display menus and react to mouse events. Other X
> > applications
> > including emacs and Mozilla are quite usable over the same link. What is it
> > about
> > Swing and/or AWT that causes this horrible performance. Is there anything
> > that can
> > be done about it.
>
> So-called "lightweight toolkits" like Swing are much harder on network
> bandwidth than "heavyweight toolkits" - solving the same problem in AWT
> would help, if you can live with the limited selection of widgets. Also,
> using the LBX extension (low-bandwidth X), which is something you set
> up completely outside Java, is a good way to improve X's bandwidth usage.
>
> Nathan Meyers
> [EMAIL PROTECTED]
>
> >
> > Steve
> >
> >
> > ----------------------------------------------------------------------
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
Homepage: http://homepages.tig.com.au/~jmsalvo/
Public Key:
http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x51F47D34
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
