[bind10-dev] MSGQ-NG requirements

[JINMEI Tatuya / 神明達哉]

At Thu, 5 Apr 2012 11:03:45 +0200,
Michal 'vorner' Vaner <michal.vaner at nic.cz> wrote:

> 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.

Some random comments:

- I was not sure if a central server is an assumption (or is it an
  implementation issue?)
- Regarding high-load support, I wonder whether we have any expected
  scale where this generic msgq is applicable, or whether it's
  "infinite".  I also wonder performance requirement in terms of
  transaction speed.
- "Multi-component support" and "Use of the bus from python-C++
  wrappers" were simply not easy to understand for me.  For a "short
  look", I didn't spend much time to try to understand them, so it's
  just an impression rather than specific points to improve.  It's
  just me, or some clarification help.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.