* Thomas Swan <[EMAIL PROTECTED]> [010313 13:37] wrote:
>
> >On reciept of the info signal, the backends collaborate to piece
> >together a status file. The status file is given a temporay name.
> >When complete the status file is rename(2)'d over a well known
> >file.
>
> Reporting to files, particularly well known ones, could lead to race
> conditions.
>
> All in all, I think your better off passing messages through pipes or a
> similar communication method.
>
> I really liked the idea of a "server" that could parse/analyze data from
> multiple backends.
>
> My 2/100 worth...
Take a few moments to think about the semantics of rename(2).
Yes, you would still need syncronization between the backend
processes to do this correctly, but not any external app.
The external app can just open the file, assuming it exists it
will always have a complete and consistant snapshot of whatever
the backends agreed on.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
