The creator of SQLite actually gave a talk about using an SQLite database as a means for IPC (it was available on youtube, maybe you can find it). If you want an 'sqlit-ish' way, why not use that trick?
One advantage of using SQLite is that debugging / backtracing becomes easier. Since your messages are passed through a database, you can easily backtrace IPC calls (by perhaps setting a 'complete' field instead of deleting a IPC message) and you can inject IPC messages easily by using the SQLite CLI. On Tue, Jun 15, 2010 at 5:01 PM, Igor Tandetnik <itandet...@mvps.org> wrote: > arno <a...@renevier.net> wrote: >> I have two processes connecting to a database. Both can modify database. When >> some process modify database, I want the other to be notified (so, it can >> reload data). >> Currently, I use unix sockets, so a process can notify all listener process >> that something has changed. But I wonder if there's a better way to achieve >> that. >> I've tried to a create a custom function (with sqlite3_create_function), and >> use triggers. But unfortunately, my trigger was executed for the modifying >> process. > > SQLite is not an interprocess communication mechanism. Any notification of > the sort you envision must be done outside of SQLite. > -- > Igor Tandetnik > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
