The doxy for ecore_file_download() say: The @p status parameter of @p completion_cb will be filled with the status of the download (200, 404,...).
Is this true? I never see a status different than 0 or 1. Is this a bug in the result value or just an error in the doxy? It would be really usefull to have the status as staten in the doxy, in my app I have to check to downloaded file size to understand if the file is ok or it just downloaded an html file that say some error. Thanks DaveMDS 2011/2/16 sangho park <[email protected]>: > yes, I've tested the API. > I added a simple example to 'ecore/examples/ecore_file_download_example.c'. > > pls review again~ > > > On Tue, Feb 15, 2011 at 11:04 PM, Vincent Torri <[email protected]> wrote: > >> >> >> On Tue, 15 Feb 2011, Cedric BAIL wrote: >> >> Hi, >>> >>> On Tue, Feb 15, 2011 at 1:15 PM, sangho park <[email protected]> wrote: >>> >>>> sure~ I modified. >>>> I hope that this patch is the last.. :) >>>> >>> >>> Sounds good to me. Will feel better if someone else also do another >>> review before applying to svn. If nobody does before tomorrow, I will >>> commit it to svn and wait for people to complain :-). >>> >> >> is it tested (i won't have time today) ? Also, a small test example would >> be nice >> >> Vincent >> > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
