Just thought it was a funny story to share. Was at my friends company
yesterday poking around and after doing a bit of back and forth with the dev
group found myself being forced to describe some of the differences between
the action based frameworks and tapestry.

The funny part was that I started off saying that some of the others were
action based, and did catch myself saying tapestry was component based...But
upon further thought decided that components really had nothing to do with
it as they just happened to be there, could be a page or service for all we
care. The only description that fit was calling it an "object oriented"
framework. Heh.

j

Reply via email to