Topics of !MiniTalk
by mpo
- General introduction to generic interfaces and roles inside the flow part of Cocoon
native continuation vs WebContinuation
WebContinuation and Manager
Interpeter and YourImplementations
Question: has WebContinuation Management been checked for race conditions?
- Interface to sitemap: start and continue
- Proposing name changes
java: Interpreter --> FlowProcessor
java: AbstractIntrepreter --> AbstractFlowProcessor
xconf: <flow-interpreters> --> <flow-processors>
java: Interpreter.callFunction() --> FlowProcessor.initiateFlow()
java: Interpreter.handleContinuation() --> FlowProcessor.continueFlow()
xmap: map:call/@function --> map:initiate/@flow
xmap: map:call/@continuation --> map:continue/@flow
- Question: do we need a mix of flowProcessors in one webapp?
Remaining aspects of WebContinuation Management
- End of live (gracefull==?, forcefull==expires, end-of-use-case==invalidate)
- End of live callback to interpreter
- Concurrency
- Access Control
Additional comments:
- (yours here)
Outcome of the hackathon discussion:
(check back after monday 6th October)