You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:
In this episode, I’m at SAP TechEd 2009 and jointed by SAP’s Thomas Jung and Colgate-Palmolive’s Ed Herrmann. Both, more importantly, are the the hosts of Enterprise Geeks. While this isn’t strictly an RIA themed episode, our guests Thomas Jung and Ed Hermann hit on many of the favored topics for RIA Weekly, including enterprise applications and HTML 5. We get into some HTML 5 talk as well. We discuss:
- The Enterprise Geek show – topics they’ve sussed out in the SAP, enterprise, and tech world and the emerging role the podcast plays in the SAP community.
- What they think of Google Wave: business uses for Wave and some theoretic thinking on what you’d have to do to start using it at a “normal” enterprise like, say, Colgate-Palmolive.
- What’s up with HTML 5? Does the <canvas/> tag make these two excited about dancing charts in HTML?
Disclosure: SAP is a client and paid T&E to TechEd.
Listened to the podcast this morning, and really liked it!
I would like to comment on a few topics.
1. HTML versus plugins.
One advantage of HTML 5, is that it provides a smooth migration path, from "normal" web applications to RIA's. Transitioning from a HTML based web app to a Flex based app for example is much harder.
2. Multiheaded applications (Web Dynpro)
Yes, theoretically being able to switch the renderer can be an advantage, but it also leads to certain limitations.
– It's hard to add new controls to WD, because those controls would have to be supported for all rendering technologies.
– Essentially WD is server side rendering technology, very similiar to JSF. This limits interactivity, because every click typically requires at least on server roundtrip.
-These frameworks have typically a higher memory overhead per user because they are relatively stateful. For JSF check for example http://ptrthomas.wordpress.com/2009/01/14/seam-js…. Being stateful has serious implications in cloud based architectures, e.g. it's much harder to scale.
Disclaimer: I'm not speaking for my employer.