Linux

Oh, you are writing a real file. And making new AJAX requests every time to download the complete file; you might have said so. And replacing the entire file each time, not writing "1,2,3,..."

That fseek does nothing, delete it; you start over at the beginning of the file every time you re-open it anyway.

Make sure your logic's working. I think there might be precedence problems in

Code:

(i == inc && j<=100)

, make it

Code:

((i == inc) && (j<=100))

...and make sure that j ever gets incremented at all. You could test your server-side code by opening the file for append instead of overwrite, and doing fprintf(file, "%d\n", j); so that it adds numbers line by line. If it works right the .txt should contain the numbers in sequence by the end.

yes I tried that, it do print 1,2...100.....No problem in logic.....rather I also put sleep(1); and the progress bar increments after 1 sec till 100, but this happens after the file has actually being copied. So, seems there is some buffering issue.

The OS doesn't buffer unless you ask it to, and you're not, so it may be your web server. What is it?

Ya, web server or CGI, web server is lighttpd.

---------- Post updated at 01:29 PM ---------- Previous update was at 01:25 PM ----------

Now I was following a different approach. I am using a CGI which outputs
system ("ls -la /tmp/lighttpd-upload* | awk {'print $5'} | wc -l");
and my ajax reads something like this 0,1,2,3.....22,23(=MAX),22,....2,1,0 (depending on the file size). However, this is not an efficient way as MAX couldn't be known beforehand so progress bar couldn't be incremented appropriately. Therefore, I like the previous approach, but that is not working at all.Do you have any other idea??
I really appreciate your help.

I am not familiar with lighttpd, but it does a lot of I/O tricks to keep performance low, that'd be the place to start looking. Try and disable caching/optimization for certain files or folders.