functions.

of the first message in the thread, or 0 if unknown (e.g. legacy message). When
a new message is created, the thread_id value of the message being replied-to
will be used, else if the new msg is not a reply, then the new message's number
will be the value used for the thread_id.
This "thread-id" feature (Deuce's idea) allows threads with a common parent to
remain logically grouped after the original messages in the thread have been
purged (though the original hiearchy will start to be lost).

NULL because the get function is called on the prototype which isn't
constructed (via the constructor).

client can read the associated message.

Should make moderation/view own deleted/etc handing way easier for JS
developers.

MsgBase.get_msg_tail() which will optimize the get to avoid re-reading
the headers.  When this is specified, the message number or id is not
required (but specifying it won't hurt anything and will allow backward
compatibility).

I'm not sure I need to lock the header here, but I think I might (if nothing
else, to ensure the message still exists).

to expose via JS: sender_userid, sender_server, and sender_time.

resolve callbacks.

value, some fixes).

code.

functions when an excpetion is pending.

Some work still needs to be done on js_msgbase.c,  js_user.c, and mailsrvr.c

Perviously, if the argument to a number of bbs.* functions was not a valid
number, Synchronet would silently ignore the parameter and treat it as though
it was not specified.

The new behaviour was to use the value as a number.  However, the old code
caused the exception triggered by an inability to convert the number to
be pending until after the return (the JS_Native didn't return JS_FALSE) so
a try/catch block aorund it would not catch the exception.

The new new behaviour is to throw the exception immediately so it can be
caught and handled correctly.

signed ints such as the zone offset.

Foxes bug with commitlog.js

Only js_ValueToStringBytes() still leaks.

      on the floor of Deuce's computer room
Cyan: Rob's on his way
* Deuce throws his coffee on it.

especially through SMTP (where these values are exposed via the Originator-info
header field): SENDERUSERID, SENDERSERVER, and SERVERTIME.

This should fix Matt's problem with crashes when calling File.writeAll() with a
null value and other potential occurances of the same bug.

just locate them again every time you need them.

static properties so you can modify the prototype without creating an
instance first.

when_imported_zone_offset which are the UTC offset (minutes east of UTC)
for the respective time zone (read only).
Change LAZY_* macros to allow property flags to be specified.

subnum is uint32_t, is 65535.

if savemsg() call failed, SMB status was not saved in msgbase.status prop.
if savemsg() call failed, the recipient list array, if supplied, was still
parsed and headers created (!).
if the recipient list parsing fails, the msgbase.error string may not have been
set, now it'll be set to "Recipient list parsing failure" (if not SMB error).

supports buffers > 1024 bytes.