predictive: Predict the future, backtrack on failure

[ bsd3, data, library ] [ Propose Tags ]

This is a library for predictive scans. Its aim is to improve user experience in cases when user interactions have to be acknowledged by a remote host. It closes the gap between requesting the interaction and the remote end acknowledging it by predicting what the remote end will decide based on local information. If the prediction is wrong, it automatically backtracks to the last state known to be consistent.

Simple example: Your application displays a client-side text box, but each edit made to it has to be acknowledged by a server. However, most of the time the server will acknowledge, so your application can use this library to proceed under this assumption and only backtrack, if the server disagrees.


[Skip to Readme]

Modules

[Index]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.1.0
Change log CHANGELOG.md
Dependencies base (>=4.7 && <5), containers (>=0.5 && <1) [details]
License BSD-3-Clause
Copyright Copyright 2016 Ertugrul Söylemez
Author Ertugrul Söylemez <esz@posteo.de>
Maintainer Ertugrul Söylemez <esz@posteo.de>
Category Data
Home page https://github.com/esoeylemez/predictive
Bug tracker https://github.com/esoeylemez/predictive/issues
Source repo head: git clone https://github.com/esoeylemez/predictive.git
Uploaded by esz at 2016-08-22T21:11:14Z
Distributions NixOS:0.1.0
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 985 total (9 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2016-08-22 [all 1 reports]

Readme for predictive-0.1.0

[back to package description]

Predictive

This is a library for predictive scans. Its aim is to improve user experience in cases when user interactions have to be acknowledged by a remote host. It closes the gap between requesting the interaction and the remote end acknowledging it by predicting what the remote end will decide based on local information. If the prediction is wrong, it automatically backtracks to the last state known to be consistent.

Simple example: Your application displays a client-side text box, but each edit made to it has to be acknowledged by a server. However, most of the time the server will acknowledge, so your application can use this library to proceed under this assumption and only backtrack, if the server disagrees.