I have written AJAX-driven systems callign linux scripts, yes.
Quote:
Originally Posted by
xs2punit
As ajax at the client could ONLY read the file, there is no point of locking.
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.
Quote:
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.
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.