Your options, I guess, are to either put it in the Visit or include
it as a hidden field in a form on the confirmation page. The latter
option scares me because I think it would serialize the whole file,
so you'd upload it, send it back in the confirmation page, and then
rewind to get it again before finally doing anything with it. I
suppose you could make it persistent in the confirmation page so that
it would be there when you get the submit, but that puts a reference
in the session just the same as using Visit explicitly.
Todd
P.S. I'm about 75% sure of everything I just said, but this is by far
the longest answer I've ever given on this forum, so if someone could
confirm what I just said or set me straight, I would appreciate it
and Sean probably would, too. :-)
On Jul 5, 2005, at 11:58 AM, Sean LeBlanc wrote:
On 07-05 11:31, Todd O'Bryan wrote:
I would suggest you do the confirmation before you have them set the
file. Once the listener fires for an Upload component, the file has
already made the trip to the server. Backing out now just wastes
bandwidth.
<snip>
I agree, however, I have a requirement to do this, unfortunately. I
guess
the other option is Javascript popup during click to submit, but
that has
problems, too.
The file in question is small and the network is all local, so the
bandwidth
is a non-issue.
That being the case, how would I go about carrying this data from
one page
to another?
--
Sean LeBlanc:[EMAIL PROTECTED]
I count him braver who overcomes his desires than him who conquers his
enemies; for the hardest victory is the victory over self.
-Aristotle
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
