I was thinking... wouldn't a "automate tcp" be useful?

I mean something that just accepts TCP connections and then talks the
"automate stdio" protocol: having an always-on server listening on
127.0.0.1:something could be very nice e.g. from PHP access, when it
would be difficult to maintain an open "automate stdio" available from
all workers.

Or there is some problem against that I cannot see right now?

    Lapo

PS: this could be easily done using "tcpserver" but that would accept
only one connection at a time, for file-locking problems, isn't that so?



_______________________________________________
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel

Reply via email to