Re: What is transient metadata ?

Holger,
I believe the transient metadata solve the problem properly. Same way we 
don't provide any special bridge for declaring how the persistent 
metadata is computed automaticaly - java module takes responsibility of 
that - we take the same approach with transient metadata. This gives us 
the possibility to decide when metadata shell be computed, which is 
important and should not be isolated, otherwise performing a complex 
query on the metadata could result in parsing all the sourcecode in the 
project in order to find out if it needs to recompute something. The 
approach that we took is that java module has to decide if something 
needs to be recomputed and if so, it does it.
Martin

Holger Krug wrote:
> On Fri, Jun 28, 2002 at 03:08:23PM +0200, Svata Dedic wrote:
> 
> 
>>Interesting - how would you imagine the `functional rules' ? So
>>instead of giving rules, I will hook in a metadata producing
>>machine.
> 
> 
> When you are able to split the machine into two parts, one determining
> *how* to compute metadata and the other determining *when* meta-data
> shall be computed, than the first one is what I mean with `functional
> rules'.
> 
> 
>>Ideally, a client using JMI reflection could extract that data without 
>>knowing they're transient.
> 
> 
> Yes.
>