On 07/08/14 23:36, Jean-Philippe Ouellet wrote:
What you are trying is not new, but crazy and sh*t seem pretty spot on.
Your description, not mine.
There's even a wikipedia article dedicated to how dumb this is!
>From http://en.wikipedia.org/wiki/Database-as-IPC:
In computer programming, Database-as-IPC is an anti-pattern where
a database is used as the message queue for routine interprocess
communication in a situation where a lightweight IPC mechanism
such as sockets would be more suitable. Using a database for this
kind of message passing is extremely inefficient compared to other
IPC methods and often introduces serious long-term maintenance
issues, but this method enjoys a measure of popularity because
the database operations are more widely understood than 'proper'
IPC mechanisms.[1]
On Tue, Jul 08, 2014 at 06:59:57PM +0200, Gustav Fransson Nyvell wrote:
mmap seems very low-level and dangerous
...
I want to add to the kernel is this easy to use style of messaging so
that common programs can use it, immediately.
Right... mmap is "low-level and dangerous", so lets add large
arbitrary shit to the kernel instead! So like kdbus, except
implemented in the worst way possible? Please stop.
think libmessage would be a good fit it just needs a better backend.
No, it needs to disappear, and this conversation needs to end.
The system you are proposing is not at all the system you need,
nor the system you'd want if you understood the problem better.
I think this is sorely needed, as well.
Some other people have agreed with you, which is why this problem
has already been tackled (in ways MUCH better than you are proposing)
by people who put actual thought into the design phase before writing
the dozens of different messaging queue/bus systems out there.
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 quite obvious that you have no idea what you're talking about.
It's like an internal network for the kernel.
First of all, this has nothing to do with networks.
Second of all, this has nothing to do with 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.
Good bye, troll.
Did you write that WP article? Anyway, I don't know enough of how the
kernel works to use it properly for this situation, though it's nice to
see the list is working as expected.
--
This e-mail is confidential and may not be shared with anyone other than
recipient(s) without written permission from sender.
