Subj : bbs.smb_curmsg in messages to you
To   : Nightfox
From : Digital Man
Date : Tue May 14 2013 05:53 pm

  Re: bbs.smb_curmsg in messages to you
  By: Nightfox to Digital Man on Sun May 12 2013 07:30 pm

 >   Re: bbs.smb_curmsg in messages to you
 >   By: Digital Man to Nightfox on Sun May 12 2013 13:44:16
 >
 >  DM> What about the bbs.msg_number property? It behaving as you would
 >  DM> expect?
 >
 > I haven't tried using bbs.msg_number yet, but so far it seems to be
 > behaving as I would expect.  But I'm a little hesitant to use it for
 > MsgBase.get_msg_header(), since it doesn't change when new messages are
 > added or deleted.  SlyEdit (currently) uses message indexes, since I've
 > always thought that was the most reliable way to reference a message.

No, it's actually the opposite. Think of the message number like a "serial 
number" for the message. It won't be reused and never expires.

 > I
 > remember a discussion a few months ago that I think involved using
 > bbs.msg_number in a calculation to come up with an absolute message number,
 > which wouldn't necessarily be for a message that exists.

That was an unrelated subject, but yes, there can be "wholes" in the message 
numbers (where a message once existed but was deleted).

 > Can
 > bbs.msg_number be used directly in MsgBase.get_msg_header (with the
 > by_offset parameter as false)?

Yes, exactly.

The bbs.msg_offset property will probably just be removed since it doesn't 
provide any benefit.

                                            digital man

Synchronet "Real Fact" #66:
SEXYZ is as a 32-bit replacement for [F]DSZ, CE-XYZ and other protocol drivers.
Norco, CA WX: 78.3øF, 38.0% humidity, 13 mph NNW wind, 0.00 inches rain/24hrs

.