[ https://issues.apache.org/jira/browse/ISIS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882328#comment-13882328 ]
ASF subversion and git services commented on ISIS-660: ------------------------------------------------------ Commit b1f1329ba626fcc1c3ccd959c9f4971eaff1895f in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b1f1329 ] ISIS-592,ISIS-593,ISIS-640,ISIS-659,ISIS-660: renaming... ... ViewModelSupport to MementoService > Profiling support and also infrastructure for background (async job) support > ---------------------------------------------------------------------------- > > Key: ISIS-660 > URL: https://issues.apache.org/jira/browse/ISIS-660 > Project: Isis > Issue Type: New Feature > Components: Archetype: Simple WRJ, Archetype: ToDoApp WRJ, Core, > Objectstore: JDO > Affects Versions: archetype-simple-wrj-1.3.1, > archtype-quickstart-wrj-1.3.1, objectstore-jdo-1.3.0, core-1.3.0 > Reporter: Dan Haywood > Assignee: Dan Haywood > Priority: Minor > Fix For: archetype-simple-wrj-1.4.0, > archetype-quickstart-wrj-1.4.0, objectstore-jdo-1.4.0, core-1.4.0 > > > Two use cases envisaged: > 1. profiling of the application > 2. as a handle for long-running async calls. Can envisage a contributed > collection that would list long-running async calls associated with a > persisted Interaction. > The request-scoped InteractionContext provides context information to the > caller. By default this is an in-memory representation, discarded once done. > The complementary InteractionFactory interface allows the instantiationof the > Interaction to be delegated. So the other part of this ticket is a JDO > implementation allowing the Interactions to be persisted and thereby queried. > With this done, any action invocation will also be recorded as a persisted > Interaction object. -- This message was sent by Atlassian JIRA (v6.1.5#6160)