Linux

Thanks for your reply. So, let me see what I can do, will get back again.

---------- Post updated at 02:12 PM ---------- Previous update was at 02:09 PM ----------

So, do you have any idea about Ajax? Any suggestion? I need to send a variable basically from server to client. Ajax can read .xml and .txt files. But I think it is not working the way I want. As, I want to read the data by Ajax each time the server writes to the file, instead when it has completed the process of writing. To add here, I REPLACE my text not add the data, so at a time my text file just have one value out of 1 to 100.
Moreover, although I am replacing my text and data could be read only once whole values are written, but the strange part here is that my Ajax could still read all the values one by one.
For this I tried putting the sleep(1); in between data write to file, and here my progress bar incremented after each 1 second. However this is not desirable as this process initiated after the whole file write not at the moment it was written

Even if you do manage to transmit this variable to the AJAX script somehow it's going to be a very awkward solution involving lots of retries, handfuls to dozens to hundreds more HTML retrievals than really necessary, etc. This should be solved on the server end, not the client. Instead of a rube goldberg system to check if an EOF was the real EOF, just don't EOF unless you mean it when sending the file to the client!

Advisory locking, as already said, is the way to do this. The server-side script that writes the file should always keep the very last section of the file locked. When it finishes writing another block, lock it, unlock the one before, write more, lock, unlock, etc. Once it's finally done,unlock the file completely.

The server-side script that reads the file should do much the same: always lock the section before it reads it. If the writer program doesn't have data ready for it, it'll be made to wait until the writer unlocks it. So lock a section, read it, unlock it, lock the next section, read it, unlock, repeat until EOF.

The relevant function call is flock.

I do not want to lock anything. That is not the issue. Issue is server doesn't release the file to be read.

Clearly. You should, though. Otherwise you're going to hit all the pitfalls we've been telling you about repeatedly, and all you'll be doing by doing it in AJAX instead is building your own slower, buggier, flock-over-http protocol from the ground up. Doesn't release the file? What error do you get when you try to retrieve it -- does it think the file's not present at all, or give 'permission denied', etc. Either is quite odd, most UNIX systems don't do mandatory locking of open files, nor play tricks to hide files until they're complete; what system are you using?

My issue is not that my data is getting corrupted, my issue is that my data is not written and read the way I want.
My server writes to the file and client reads the file. As ajax at the client could ONLY read the file, there is no point of locking.

Well regarding "file release" thing: I mean that the data is not available while it is getting updates, so it seems that the file is being held until whole process is completed.
ie:
if i write 1,2....100 in text file , intead of the changing values 1,2,3 etc; i get
1,2,..100 at ONCE not one by one ie not at the time when it is UPDATED.

I am using Linux, you are write that Linux doesn't hold/hide the file. So, may be this is not a Linux issue. In case you have knowledge of Ajax, let me know if can discuss this further.

Thanks

hope this makes sense to you.

I have written AJAX-driven systems callign linux scripts, yes. We've told you over and over what the locking's for and why you need it for reading a file that something else is appending to. Again, linux doesn't hold the file. Locking of that sort is opt-in and you're not opting. The behavior you describe seems more and more strange...

By file do you mean a real, genuine, unparsed, honest-to-god file? Or do you actually mean your AJAX is reading output fetched from a server-side script? They act very differently, and the latter would act like what you're saying, and wouldn't need locking like you're saying. The web browser would just wait for its output. If you're reading script output, and it's arriving all at once, it's probably line-buffering. Flush the output on the server side whenever you really want the script to send. Or, just write a newline, which should flush it too.

well you can refer to this File upload progress bar - Stack Overflow