"Lie Ryan" <[EMAIL PROTECTED]> wrote
sharing a database and using one table for input and another
for output. The server polls the input table and writes output to
In a much simpler situation, even a communicating from a plain file
could be enough. In the daemon's program folder, there'll be two
files:
The problem with text files for this is that it seriously limits
the number of clients because locking is applied at the file
level, whereas with a database locking is generally applied
at the row level. Also databases tend to support triggers that
only fire the server process when something actually gets
written. For files you really need to poll the file (although
some OS might support select() monitoring of a file - but
by then sockets are easier! :-)
But if you only have one client then a file will certainly work
just as well.
Alan G
_______________________________________________
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
