I love your pictures! I need to go shopping badly as well. I can't wait until Paxton is old enough to play with his cousins. How are your pizza days coming along?
Are webapp frameworks more elaborate than they need to be? It's not hard to find web application frameworks that simultaneously claim to offer power and simplicity -- a great combination, but a rare one too -- and some of them are based on the idea of "components" or "controls": JSF is touted to be the ultimate component framework for Java web application programming. Tapestry claims to be based on the idea of component development. And across enemy lines, ASP.NET generated a whole new market for web components. With this, Michael Jouravlev begins his investigation into web components, but with a crucial difference: he omits the framework. In the Feature Article on today's front page, Building Web Components Without a Component Framework, he tears down the idea of a web component to its absolute basics: a resource, identified with a unique location, that maintains state, responds to events, and is able to render itself. He continues:What is new in that, you may wonder? Nothing but good old HTTP with a twist. If you use JSP as the presentation layer for your web applications, this article may open some new possibilities. _____________ mikemathew Search engine
3 comments:
Too bad I looked at it too late or Ella and I would have come:)
I love your pictures! I need to go shopping badly as well. I can't wait until Paxton is old enough to play with his cousins. How are your pizza days coming along?
Are webapp frameworks more elaborate than they need to be?
It's not hard to find web application frameworks that simultaneously claim to offer power and simplicity -- a great combination, but a rare one too -- and some of them are based on the idea of "components" or "controls":
JSF is touted to be the ultimate component framework for Java web application programming. Tapestry claims to be based on the idea of component development. And across enemy lines, ASP.NET generated a whole new market for web components.
With this, Michael Jouravlev begins his investigation into web components, but with a crucial difference: he omits the framework. In the Feature Article on today's front page, Building Web Components Without a Component Framework, he tears down the idea of a web component to its absolute basics: a resource, identified with a unique location, that maintains state, responds to events, and is able to render itself. He continues:What is new in that, you may wonder? Nothing but good old HTTP with a twist. If you use JSP as the presentation layer for your web applications, this article may open some new possibilities.
_____________
mikemathew
Search engine
Post a Comment