[
http://issues.ops4j.org/browse/QI-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531#action_13531
]
Rickard Öberg commented on QI-83:
---------------------------------
This is only important for fat clients which have in-process EntityStore
mapping against the server. Which we don't have.
> Implement loading policies
> --------------------------
>
> Key: QI-83
> URL: http://issues.ops4j.org/browse/QI-83
> Project: Qi4j
> Issue Type: New Feature
> Components: API
> Affects Versions: 0.3
> Reporter: Rickard Öberg
> Assignee: Rickard Öberg
>
> Currently all state from entitystores is lazyloaded. For really performant
> applications this is not good enough, and we need a way to do eagerloading in
> a controlled fashion on a per-usecase basis.
> I would suggest implementing Loading Policies: the ability to attach a
> specification to the UnitOfWork which tells the entitystore what state to
> load in one go. The specification can either be declarative (as in declaring
> what properties and graph depth to load) or named (as in specifying a name
> which is then explicitly known by the entitystore or a plugin to it).
> This can radically improve performance in many cases, especially for remote
> clients.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
