On Wed, 12 Mar 2003 21:38, Leo Sutic wrote:
> I'm trying to find some common ground - it is complicated mostly because
> while I know what an interceptor *is* I have no clue at all just what
> difficulties I would run up against when trying to implement it.

They are actually relatively easy to implement - just hard to manage 
generically ;)

> I found this:
>
>     http://www.java.no/web/moter/moteSep02/AOP_files/frame.html

thats a good one. I sent another to Berin recently ... Berin can you post the 
link?

> Now, if a lifecycle package could be constructed that would support
> everything described there, would it be enough?

sure - if it could support all that then it would not suck technically. Still 
has no place in framework CVS though - especially if it has not had time to 
mature and settle (Remember even the current framework took at least 3 years 
to settle and we got oodles wrong with that).

Though I believe Rickard �bergs is going to release his toolkit soon (though 
he was going to do it in december ... then january ...) so you may want to 
wait for that. I susepct it will be fairly solid - though maybe "gritty" 
tech. There is also nanning at sourceforge that may form a base if you want 
to start it imediately though nanning is not really scalable enough for fine 
grain components.

I am working on a toolkit also to do this stuff but it is no where near mature 
enough at this stage. A basic overview that assumes exisitng knowledge

http://spice.sourceforge.net/xinvoke/selectors.html
http://spice.sourceforge.net/xinvoke/interceptor.html

But thats not going to be worked on for a while. 

BTW I dont object to it being released as an excalibur component or whatever 
but not as part of framework or in anyway given the same level of maturity or 
support as framework.

-- 
Cheers,

Peter Donald
--------------------------------------------------
 Logic: The art of being wrong with confidence...
--------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to