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

Flash map / flash cookie support #33

Open
greenrd opened this issue Oct 6, 2012 · 1 comment
Open

Flash map / flash cookie support #33

greenrd opened this issue Oct 6, 2012 · 1 comment

Comments

@greenrd
Copy link
Contributor

greenrd commented Oct 6, 2012

The idea is that you have ephemeral state which only exists for the next request and is then deleted. This can be used for e.g. redirecting to another page and displaying a "success" widget - the success message would be stored in the flash map / flash cookie.

A problem with this (at least, as they are implemented in Play 2.0.1) is it doesn't play well with multiple tabs being used by the same user at the same time.

Scalatra does already have a flash map implementation but I'm unclear on how this could be used from Bowler.

@greenrd
Copy link
Contributor Author

greenrd commented Oct 6, 2012

Note: The reason why you don't just use ordinary HTTP parameters for such use cases is they're not ephemeral enough - you don't want the same message to be displayed twice.

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