Re: [Erlyaws-list] monitoring process for failed file uploads

[Steve V. <vi...@ie...>]

I'm investigating this and will get back to you later.

--steve

On Thu, Oct 12, 2017 at 1:15 PM, Nuku Ameyibor <na...@st...>
wrote:

> hi  list ,
>
> i am using *yaws_multipart:read_multipart_form(Arg, Options)* to upload
> files from web forms onto a server .
> i am using the temp file option in this scenario .
> i was wondering if there is a best practice for dealing with files which
> may not be fully uploaded due to errors which may happen  during upload .
> reason may be large file sizes,disconnected client etc...
> the    *{error, Reason} -> *
>             ....
> response  doesn't seem to expose the filename(s) but only the field name
> of the currently processed file .
> this makes it difficult to  know which temp file had an issue .
> i would  like to delete those errroneous files in my case .
> the source code yaws_multipart.erl shows the following ii guess for the
> size checks i think
>
>
>
>
>
>
>
>
>
>
>
> *check_param_size(State, NewSize) ->     case State#upload.max_file_size
> of         undefined -> ok;         MaxSizeInBytes ->             case
> NewSize > MaxSizeInBytes of                 true ->
> {error, io_lib:format("~p is too large",
>         [State#upload.param_name])};                 false ->
>       ok             end     end.*
>
> will it be better to return the file name in addition to the param name .
> but that still does not solve the problem of disconnected clients .
> any thoughts will be appreciated !!!
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Erlyaws-list mailing list
> Erl...@li...
> https://lists.sourceforge.net/lists/listinfo/erlyaws-list
>
>