Submitted by Justin (not verified) on February 6, 2007 - 9:37pm.
I'm not sure I really understand what a widget is I don't think. Isn't it just a piece of display code that draws from a source other than the requested server? I can't really figure how your assertions fit into this model. Basically the 'page' is still just a jumble of HTML rendered by the browser. Ajax allows for some dynamism in the display by introducing a pseudo client-server model, but the website remains stateless in a purely technical sense, right? What am I missing here?
I have to admit when I hear "widget" I feel the same bile rising as when I hear marketing buzzword. To me it doesn't seem like anything revolutionary at all is happening. Again, what am I missing?
Huh?
I'm not sure I really understand what a widget is I don't think. Isn't it just a piece of display code that draws from a source other than the requested server? I can't really figure how your assertions fit into this model. Basically the 'page' is still just a jumble of HTML rendered by the browser. Ajax allows for some dynamism in the display by introducing a pseudo client-server model, but the website remains stateless in a purely technical sense, right? What am I missing here?
I have to admit when I hear "widget" I feel the same bile rising as when I hear marketing buzzword. To me it doesn't seem like anything revolutionary at all is happening. Again, what am I missing?