Well, =CF'm not really sure about a formal to do list. We need to discuss=
a
few topics, though:
- AOPAlliance
Provide this compatibility is nice for our users, but I must say that the
AopAlliance interfaces are not well defined. A few changes could help us =
to
achieve better performance
- Semantic checking
The semantic check is not checking if the custom matcher actually impleme=
nts
the IClassMatcher interface cause this would lead us to a cyclic assembly
references. What do you think about moving the important interfaces to ot=
her
assembly? This could solve this problem but introduce more aggravations t=
o
our users.
- Caching
There are lots of points in the code that will benefit from caching. Toda=
y
Aspect# performance is far from a Good Enough. I haven't spent much time
thinking about caching, though. You could come up with a few strategies.
This is the list off top of my head, I'm sure there are plenty more topic=
s
to be covered...
Cheers,
hammett
----- Original Message -----
From: "Henry Concei=E7=E3o" <hen...@gm...>
To: <asp...@li...>
Sent: Wednesday, October 06, 2004 1:20 PM
Subject: [Aspectsharp-users] Next Iteration
Hammett, could you send to us the TODO list?
And what you guys think about start the refactoring of the Interceptor
Model?
--
Cheers,
Henry Concei=E7=E3o
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out mo=
re
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Aspectsharp-users mailing list
Asp...@li...
https://lists.sourceforge.net/lists/listinfo/aspectsharp-users
|
