On 07/08/14 11:08, Henning Brauer wrote:
* Gustav Fransson Nyvell <gus...@nyvell.se> [2014-07-06 03:22]:
I made this thing because I wanted or need a way to message between
processes that know nothing about each other, using a central name.
that's usually called a named pipe.
or an mmap'ed "file".
Without requiring any network. So, some basic message passing, across
the OS. It's implemented using sqlite3 which in my case is not good,
ok, I stop reading here.
Using a fickle rocket launcher to light a candle.
That might be the main reason why software today is so miserable.
mmap seems very low-level and dangerous for brain dead use. I'm aiming
for syslog-like use and accompanying slowness. I think using sqlite3 as
a backend is overkill and it was the first thing I picked. Maybe
tokyocabinet would be a better fit, it might be worse to setup and I'm
guessing it's not in the kernel ATM. See what I want to add to the
kernel is this easy to use style of messaging so that common programs
can use it, immediately. Like syslog is easy. I think libmessage would
be a good fit it just needs a better backend. I think this is sorely
needed, as well. A lot of bug tracking becomes much easier - I have seen
ktrace. It is much like ktrace, yet can be used for applications too.
It's like an internal network for the kernel. I know that message queues
are frowned upon yet they are very UNIX, remember JMS is from Java which
is from Sun, which you know... created Solaris, SunOS? UNIX is supposed
to be big and slow. I'm going to stop typing now due to high environment
temperatures... AKA Summer...
//Gustav
--
This e-mail is confidential and may not be shared with anyone other than
recipient(s) without written permission from sender.
