Subj : JS Object save_msg()
To   : deon
From : Digital Man
Date : Sun Dec 22 2024 13:32:29

  Re: JS Object save_msg()
  By: deon to Digital Man on Mon Dec 23 2024 07:20 am

 >   Re: JS Object save_msg()
 >   By: Digital Man to deon on Sat Dec 21 2024 04:59 pm
 >
 > Howdy,
 >
 >  > No, it doesn't. The JS when_written_time property is still a time_t
 >  > representation - I do the conversion (encoding upon assignemnt, decoding
 >  > upon use) to the SMB date storage automatically for you.
 >
 > Actually I was refering to the post implementation of your changes to
 > when_written_time - from your commit example:
 >
 > Here's an example from smbutil v of a message header posted after this
 > change:
 >   when_written     03292595 41E0 Fri Dec 20 18:22:21 2024 PST
 >
 > 0x03292595 (53028245) is the now new value of when_written_time right?

Not exactly. That's the value/format stored in msghdr_t.when_written.time (for newly added/posted messages only), but the JS message header property 'when_written_time' is still always in time_t format.

 > But I think I get you, when I read a when_written_time, it'll convert back
 > to time_t value like time()?

Correct. It's a transparent change for JS scripts/programmers.
-- 
                                            digital man (rob)

Sling Blade quote #7:
Karl: I don't reckon the Good Lord would send anybody like you to Hades.
Norco, CA WX: 68.1øF, 37.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.23-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.