Subj : JS Object save_msg()
To   : deon
From : Digital Man
Date : Thu Dec 19 2024 03:42 pm

 Re: JS Object save_msg()
 By: deon to Digital Man on Thu Dec 19 2024 08:45 pm

> Thus when when scfg -> System ->Local Time Zone equals xpTimeZone_Local(),
> they cancel each other out and age_of_posted_item() is truely however many
> seconds ago the message was stored. (utc minus 660 plus 660).
>
> If this is what is intended, then OK, I get it. Why somebody would find this
> useful I guess I dont understand.

The time zone offsets are applied to calculate the age of posted messages to account for messages received via message networks: the when_written_time value is a time_t, in UTC, but represents the parsed date/time from the originating message header (which is the local time for the time zone of the poster): it's not necessarily the current UTC time at the time of posting when posted from a different time zone.

So yes, the adjustments to calculate the message age look unnecessary when considering only locally posted messages but make sense when considering network-posted messages.
--
                                           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: 78.2�F, 21.0% humidity, 6 mph W wind, 0.00 inches rain/24hrs

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.