ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-21 05:53:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Tech white paper: brief note on event scheduling

Browse Source
This commit is contained in:
Mike Hearn 2016-11-10 12:20:30 +01:00
parent 3b6e3712b2
commit 9d93eed56d
1 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/source/whitepaper/corda-technical-whitepaper.tex
View File

@ -687,6 +687,18 @@ as for code signing we place initial focus on being able to re-use the infrastru
% TODO: Contract constraints aren't implemented yet so this design may change based on feedback. % TODO: Contract constraints aren't implemented yet so this design may change based on feedback.
\subsection{Event scheduling}\label{sec:event-scheduling}
State classes may request flows to be started at given times. When a state is considered relevant by the vault
and the implementing CorDapp is installed and whitelisted, the node may react to the passage of time by starting
new interactions with other nodes, people, or internal systems. As financial contracts often have a notion of
time in them this feature can be useful for many kinds of state transitions, for example, expiry of an option
contract, management of a default event, re-fixing of an interest rate swap and so on.
To request scheduled events, a state may implement the \texttt{SchedulableState} interface and then return a
request from the \texttt{nextScheduledActivity} function. The state will be queried when it is committed to the
vault and the scheduler will ensure the relevant flow is started at the right time.
\section{Assets and obligations} \section{Assets and obligations}
A ledger that cannot record the ownership of assets is not very useful. We define a set of classes that model A ledger that cannot record the ownership of assets is not very useful. We define a set of classes that model
@ -730,7 +742,7 @@ TODO: Complete this section
TODO TODO
\section{Integration with existing infrastructure} \section{Scalability}
TODO TODO
@ -1182,10 +1194,6 @@ are ideal for the task.
Being able to connect live data structures directly to UI toolkits also contributes to the avoidance Being able to connect live data structures directly to UI toolkits also contributes to the avoidance
of XSS exploits, XSRF exploits and similar security problems based on losing track of buffer boundaries. of XSS exploits, XSRF exploits and similar security problems based on losing track of buffer boundaries.
\section{Event scheduling}\label{sec:event-scheduling}
TODO
\section{Future work} \section{Future work}
TODO TODO