//TODO: Extensible Metadata

Topics about Tour-eiffel | //TODO: Extensible Metadata

Topics about Tour-eiffel | //TODO: Extensible Metadata — Tue, 21 Apr 2009 15:54:08 GMT

Pingback from Topics about Tour-eiffel | //TODO: Extensible Metadata

re://TODO: Extensible Metadata

TrackBack — Fri, 15 Apr 2005 17:28:00 GMT

^_^,Pretty Good!

re://TODO: Extensible Metadata

TrackBack — Sun, 10 Apr 2005 05:31:00 GMT

^_^,Pretty Good!

re: //TODO: Extensible Metadata

Diego Gonzalez — Tue, 27 Apr 2004 13:19:00 GMT

I think the most important issue for AOP is interception in instance boundaries. I mean every time you call a method, access a field, etc. If you can do that without changind the code of the intercepted class you can do AOP is a clean fashion. Of course AspectJ is a compiler that generates new code using the Java source code and the AOP declarations.

What I say about interception is only during assembly loading to change metadata. Not about changing code.

Thanks for asking about blogging, I was very busy working many projects over here and also for PAG in Microsoft Corp. so blogging has low priority in my everyday scheduler :)
I have a couple of news I'll post very shortly.

re: //TODO: Extensible Metadata

Diego Vega — Tue, 27 Apr 2004 12:33:00 GMT

Not sure myself as I am not well versed in AOP. But I think having such a powerful (dynamic) metadata facility helping you modify code behavior thru runtime interception, while it is not the same as AOP, it is exactly what you need to do AOP. Being able to add design by contract features without recompilation could be an example of AOP, as far as I see.

I just made a search on google, and I found some interesting references:

http://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=aop+interception+metadata+%2Enet

By the way, Diego, what happened to your blogging? This entry seems to be from more than four months ago!

re: //TODO: Extensible Metadata

Diego Gonzalez — Tue, 27 Apr 2004 11:48:00 GMT

I don't know if is the same as AOP. AOP is about crosscutting concerns or functionality that applies horizontally to many classes. My idea is about composing metadata (attributes) dynamically in run-time.
Probably this is closer to a complain, because the metadata in .Net is static and also there's no way to intercept the loading of the assemblies.

re: //TODO: Extensible Metadata

Diego Vega — Tue, 27 Apr 2004 04:22:00 GMT

Wouldn't this be what is usually called Aspect Oriented Programming?

re: //TODO: Extensible Metadata

sure — Fri, 02 Jan 2004 18:44:00 GMT

yes sure, agree with you

re: //TODO: Extensible Metadata

Thomas Tomiczek — Thu, 01 Jan 2004 18:24:00 GMT

::he says the problem of placing rules in
::atttribues is that he must recompile his
::code every time a rule is changed.

Hm. not sure yet, but it seems to me that this is WRONG WRONG WRONG.

I am hunting a way right now to dynamically return attributes at runtime that are determined at runtime. It looks like this is possible.