Re: [Pybeep-devel] MessageStatus?

[Sean A. <ze...@wo...>]

On Thu, 2002-03-07 at 19:24, Gabe Wachob wrote:
> Answering my own question, please confirm:
>=20
> It appears that MessageStatus is *just* for keeping track of which
> messages have been sent for the purposes of verifying things like "does
> this incoming RPY correspond to a previously sent outoing MSG?", and as
> such, we need to keep the following information in a MessageStatus queued
> up in sentMSGQueue:

Thats kind of the way I read it too=20

> *status of the message (e.g. sent, responded, etc.. maybe we have to add
> "queued, but not completely sent")
>=20
> *replylistener (because someone needs to be handed replies to a particula=
r
> outgoing msg)
>=20
> * msgno (for checking that a RPY/ANS/NUL received corresponds to the
> oldest outgoing MSG not yet completley responded to)
>=20
>=20
>=20
> I don't see any need for any other info in the MessageStatus, do you guys=
?
>=20
> There is a slight twist - the channel only adds outgoing messages to a
> queue to be written out. I'm thinking we should add two more states for a
> message to be in (besides the 5 MESSAGE_STATUS_* there are now):
>=20
> MESSAGE_STATUS_QUEUED -- its in the outgoing queue and no frames have bee=
n
> written out from it yet
>=20
> MESSAGE_STATUS_PARTIALLY_SENT -- its in the outgoing queue and some frame=
s
> of the message have been sent out, but its not completely written out.
>=20
> I actually don't know if we'll need to check for these states (they are
> functionally equivalent to MESSAGE_STATUS_NOT_SENT, no?), but they will b=
e
> extremely useful for debugging and logging.
>=20
> Make sense?
Yes=20

Sean