http://www.dalouche.com/wordpress/2006/11/18/the-typical-bleeding-edge-web-application-architecture/ Sami Dalouche's blog about Linux, Java, .NET and other bleeding-edge stuff. skoobi@free.fr Tue, 06 Jul 2010 14:31:59 +0000 http://wordpress.org/?v=2.9 hourly 1 http://www.dalouche.com/wordpress/2006/11/18/the-typical-bleeding-edge-web-application-architecture/comment-page-1/#comment-194 Sami Dalouche » HOWTO: Use Direct Web Remoting (DWR) with Spring Framework and Java5 Annotations Mon, 27 Nov 2006 10:38:23 +0000 http://samokk.is-a-geek.com/wordpress/2006/11/18/the-typical-bleeding-edge-web-application-architecture/#comment-194 [...] As a sidenote, DWR is part of the typical Bleeding Edge Web-Framework Stack that I wrote about in a previous post. Surely, not everybody uses this Stack, but it gives an idea of what the current trend in the Java world is. The current java world is full of innovation. Every 2 days, a new framework arrives on the scene, and beginners are more and more afraid of the overall complexity of the platform (if we can call this a platform, because it more looks like a set of unrelated  tools that people struggle to use together, in opposition to Microsoft .Net’s stack that we can safely call a “solution” because of the tight integration between the components). Innovation is doublessly a very good thing, and nothing should prevent innovation from happening. However, I believe it is also very important to document the best practices and tools and try to gather the community around a limited set of paradigms and frameworks. It doesn’t make sense to have a different framework for each programmer in this world. And in my humble opinion, using such an RMI-like system for communicating between Java classes and Javascript is definitely one of the best and efficient (from the developers viewpoint) practices around. Java class [...] [...] As a sidenote, DWR is part of the typical Bleeding Edge Web-Framework Stack that I wrote about in a previous post. Surely, not everybody uses this Stack, but it gives an idea of what the current trend in the Java world is. The current java world is full of innovation. Every 2 days, a new framework arrives on the scene, and beginners are more and more afraid of the overall complexity of the platform (if we can call this a platform, because it more looks like a set of unrelated  tools that people struggle to use together, in opposition to Microsoft .Net’s stack that we can safely call a “solution” because of the tight integration between the components). Innovation is doublessly a very good thing, and nothing should prevent innovation from happening. However, I believe it is also very important to document the best practices and tools and try to gather the community around a limited set of paradigms and frameworks. It doesn’t make sense to have a different framework for each programmer in this world. And in my humble opinion, using such an RMI-like system for communicating between Java classes and Javascript is definitely one of the best and efficient (from the developers viewpoint) practices around. Java class [...]

]]>