|
|
Posted by Yohan N. Leder on 06/09/06 21:49
In article <DJlig.505$fm.496@reader1.news.jippii.net>,
jkorpela@cs.tut.fi says...
> Wouldn't the solution be to store the data (contents of the file) on the
> server and insert an identifier for it into the form sent back to the user?
Or insert base64 content in an hidden field. But, however, nobody can
lock user to push the browser's back button, or close suddenly his
browser (for this, I don't like to keep temporary file on server disk)
> The robust way of retaining user input is that the form handler sends a
> response page that contains the user input as prefilled values of fields.
> For a file, you would have to play with indirection, i.e. an identifier such
> as a generated file name (on the server).
Well, so, the idea is always to go forward and avoid previous step
caching ?
Navigation:
[Reply to this message]
|