[bind10-dev] MSGQ-NG requirements

[Michal 'vorner' Vaner]

Hello

I started writing a page about what we need from the message queue system. It is
kind of requirements document at the moment (but not a formal one, I didn't
include stuff like „it needs to be able to send a message“).

It is on the address:
http://bind10.isc.org/wiki/msgqng (not linked from anywhere yet)

I want to add some ideas how to implement it to the end of the page soon, so it
will become some kind of hybrid requirements/design-hints. But I'd like feedback
for what I have already ‒ discussion pipelining.

If you think the current msgq is not optimal and you miss something and
it's not listed on the page, please, let me know and we'll discuss. If, on
the other hand, you think some of the things there definitely won't be useful or
will be harmful, say so too.

On the other hand, don't say things like „This'll be hard to implement“ yet. I'd
like to have the discussion of how to implement it and if it's worth it, but
after I add my ideas to the page (because I do have some).

We probably don't need an extensive discussion now, just a short look. But I
find the messaging system insufficient both in the functionality and in
convenience of use, I think it introduces needless slowdown and difficulty when
dealing with it. Therefore I hope to have a discussion on the F2F and deal with
it once and for ever.

Thank you

-- 
When a fly lands on the ceiling, does it do a half roll or a half loop?

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20120405/e6587f5e/attachment.bin>