On 23.Aug.2003 -- 03:48 PM, Stefano Mazzocchi wrote:
>
> On Saturday, Aug 23, 2003, at 10:17 Europe/Rome, Christian Haul wrote:
>
> >Stefano Mazzocchi wrote:
> >>On Tuesday, Aug 19, 2003, at 22:41 Europe/Rome, Christian Haul wrote:
> I'm not suggesting we add AOP to Rhino, I'm suggesting we add the
> ability to avoid concern crosscutting in the cocoon flow.
After reading Nicola Ken's message I believe this discussion is void
but I still would like to explain my position as it appears it hasn't
been clear enough.
I've started using flow very shortly after the javascript incarnation
arrived and I love flow. That is 1+ years using flow. I believed that
adding AOP to Rhino (which happens to be the javascript engine in
Cocoon) is beyond the scope of this project. Now you explained you
don't want to do that but only add it to the invokation of flow
functions. I believe that is a poor solution and does not provide
enough usefulness to solve any of your examples but the authorization
one.
However, as I said above, after reading Nicola Ken's mail I believe
this dicussion is void because it appears AOP in javascript is as easy
as saying "aspect". In addition, I believe his proposal for aspects in
the sitemap is balanced and very interesting. We should follow this
idea further.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
