[Vortex] Is vortex assuming that msg numbers on channels start at 1 and increase by 1/

[Sam Roberts]

On Wed, Nov 19, 2008 at 3:14 AM, Francis Brosnan Blazquez
<francis at aspl.es> wrote:
> You are right Sam. It is a bug. At this point Vortex Library can't reuse
> MSG numbers.
>
> I filled a bug report at:
>
> http://bugzilla.aspl.es/cgi-bin/bugzilla/show_bug.cgi?id=331

I read the report, I don't think it describes a fix to the problem, it
describes a fix to the opposite of the problem I saw.

What vortex does in terms of its message number **allocation** is
standards compliant, and as far as I know, works with other BEEP
implementations. It certainly works with beepcore-c, doesn't need any
modification, and certainly not some user-controlled message number
allocation system! Yuck! ;-)

I assume vortex already tracks which MSGs it has received on a
channel, so it can know which message numbers the local API user is
allowed to send a RPY, ERR, ANS, or NUL to.

All you need to do is when a MSG is received on a channel, make sure
that it's message number is NOT among the currently active message
numbers (instead of whats done now, which is to make sure its equal to
the number of the last MSG + 1, which is wrong).

My comment about message number reuse was just illustrative of how
flexible the RFC is in how implementations can allocate message
numbers. I haven't actually seen a beep core reuse message numbers
(even for wrapping, because have never waited for more than 2147483647
messages on a channel...).