|
I agree that the bandwidth requirements of the approach proposed in this article are a major issue. A further problem is scalability on the server side: if you have lots of sessions, rendering Swing components to images on the server side is not really effective. And what about event handling? How do you want to support Swing's event handling efficiently?
I suggest looking at the Server-side Swing approach taken by Canoo UltraLightClient. That's an approach integrating Swing into J2EE that really scales. |