Hello there! Unfortunately this approach did not solve our problem. On a
connection error, we still get a 226 - Transfer Complete code. So no matter
if the file is complete or not, we keep getting "success" status.

We are still looking for alternatives. Thanks all for the help

On Tue, Mar 2, 2010 at 9:44 AM, Niklas Gustavsson <[email protected]>wrote:

> On Tue, Mar 2, 2010 at 1:00 PM, Vinicius Carvalho
> <[email protected]> wrote:
> > I'm using 1.0.3. Ok tks. I'll give it a try. Since onuploadend does not
> have
> > this argument I wasn't able to figure out. But since its called before
> > onuploadend, I guess I could stack the value on a ThreadLocal to be
> > retrieved later.
>
> Even simpler is to use afterCommand() directly. onUploadEnd() is a
> simplified callback, but you can always use before/afterCommand()
> instead.
>
> /niklas
>

Reply via email to