On Mon, Aug 18, 2008 at 6:33 AM, Rickard Öberg <[EMAIL PROTECTED]> wrote:
> Right now Entity metadata such as version and last-modified is handled > separately from other Properties. This makes it impossible to use > queries with them, which sometimes would be convenient (e.g. "list all > entities modified after date X"). My first reaction was; Sure, this sounds like a really good idea. > For caching purposes there are also other kinds of metadata > that would make sense to add as Entity Properties, such as Expires > and MaxAge. And then, this I am not equally sure about. In fact, isn't this a thing at "Entity Type" level, which actual times are handled internally?? I.e. metaInfo should be enough, no? But you mention "per instance" settings, which I am not totally convinced is useful and/or feasible in actual code. Perhaps there is use-cases, but we are then looking at a "Cache Aspect" of an Entity and my question would then be; What other aspects are there? And wouldn't that lead to a more generic approach, instead of "hard coded" onto the Entity type? Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
