Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persistence Best Practices #18

Open
urs-of-the-backwoods opened this issue Aug 5, 2013 · 0 comments
Open

Persistence Best Practices #18

urs-of-the-backwoods opened this issue Aug 5, 2013 · 0 comments

Comments

@urs-of-the-backwoods
Copy link
Contributor

A normal web package (and Yesod or Dojokit are no exceptions) handle updates of persistent data in a submit action. The FRP approach shines by doing all updates of complex data relationships immediately.

See the CRUD example for how a typical FRP application might look like.

It is OK that HWebUI takes another approach. In the end Yesod and Dojokit are tools to achieve a new way of GUI programming which should be more Haskell like.

But how can those both approaches be combined in a way that the user knows exactly the state of the data on screen (easy due to automatic updates) and on disk (not so easy).

Develop some ideas and show use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant