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

Collect data between redirects #30

Open
KES777 opened this issue Sep 10, 2015 · 3 comments
Open

Collect data between redirects #30

KES777 opened this issue Sep 10, 2015 · 3 comments

Comments

@KES777
Copy link
Contributor

KES777 commented Sep 10, 2015

The problem I have run into with Plack::Middleware::Debug::Log4perl

The log messages are not displayed that were logged while processing POST data, when I POST to page that redirect (302) back to page with this form
When redirect occours the collected data in DebugPanel must be saved somewhere (maybe in session???) and displayed them on redirecting page.

But this is applyed also to 'Request variables', 'Response', 'Environment', 'Memory', 'Timer', etc.
They must show values for those two requests

  1. POST. When I try to save form
  2. GET. When form is saved and result page is showed
@miyagawa
Copy link
Owner

I agree this is a nice addition, but you should better refrain from using the word "must" in such a way you demand the feature to be implemented for free. Open source is open source, and a feature won't be added until someone implements it.

By the way there is https://github.com/stevan/p5-plack-debugger that has a completely different architecture on saving the debug related data and retrieve them via JavaScript API.

@KES777
Copy link
Contributor Author

KES777 commented Sep 10, 2015

They must = Panels must
under MUST I mean 'panel must work in this way' if this feature will be implemented by someone
I do not mean you MUST implement it.
Maybe some one see this good idea and implement. Maybe I will notice in future this mine idea and implement.

In other case idea will be forgotten

@miyagawa
Copy link
Owner

In other case idea will be forgotten

No, you don't need to use the word "must" to make some idea not forgotten. It will be forgotten if nobody wants to write it, no matter how it was worded :)

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

No branches or pull requests

2 participants