Hi All,
Are WBA's that run under IE's sandbox, or that run under partial trust, can be compared to Java applets's Do they behave same How about the performance for WBA Are they better than Java Applets
Hi All,
Are WBA's that run under IE's sandbox, or that run under partial trust, can be compared to Java applets's Do they behave same How about the performance for WBA Are they better than Java Applets
WBA vs Java Applet
Peter Richard
Mark Groves
WBA is an offering that enables you to take advantage of the richness of WPF on the web (by providing seamless web deployment, browser hosting, and the security sandbox). A few key benefits to using WBAs:
For more information about WBAs, Karen Corby's whitepaper has the details: http://msdn.microsoft.com/windowsvista/default.aspx pull=/library/en-us/dnlong/html/wpfandwbas.asp.
Pramod V
Boywonder0337
A Java applet can be page embedded like a Flash or Shockwave application , without to be inside a frame of the page . A WBA is really like a web page having only one applet...
But Java applets were a disaster (with the "help" of Microsoft that makes its strategic option for ASP - a thin client ). We have only a few Java applets working now (comparing with the number of Flash movies).
The future of WBA will be the same of Java applets Who knows
My strategy and recomendation is the use of popup web applications (not page embedded) using the ClickOnce architecture. A WBA/WinFX application - fat client -can have many Mbs and is good for the user to know its size and to have the option to download it or not. Like you can see at the many demos of our tutorials about WPF (basic and game creation) at:
http://www.dmu.com
Big and unknowed dowloads were one of the causes of the disaster of Java applets and Director/Shockwave -fat clients . It's true that now we have better and rapid comm lines...
lgrainger
thanks,
matt
Raymundo Chapa G
They mostly differ by their underlying technology (WBA is .NET and WinFX, Java Applet is ... Java).
Regarding the performance, it's not easy to benchmark 2 technologies ... people tried to benchmark .NET against Java and that started the flame wars.