Subj : Re: Dynamic COntent and Database
To   : All
From : HECTOR SANTOS
Date : Thu Jan 31 2019 07:10 pm

Date: Sat, 12 Mar 2005 20:45:24 -0400
From: HECTOR SANTOS
To: CHRIS CRANFORD
Subject: Re: Dynamic COntent and Database
Newsgroups: win.server.wish.list
Message-ID: <1110678681.33.1110530484@winserver.com>
References:  <1110530484.33.1110267990@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 65

Since the dates are 100% on server-side locality and all functionality that
I can see would based on local time, I don't think GMT applies or is
necessary.

Based on experience across the board, for something like this, it would make
it more "difficult" for you (sysop, web master) to develop time logic based
on GMT.

There only place I see GMT would be required is where you are doing some
logical time comparison based on the user's side.

Do you have an example where GMT applies?

In any case, there is GMT based macros in WCT.  The #GETTIME#  macro (see
new WCT macros added for 451.3 in AUP.CHM) is the same used by the
JavaScript "getTime()" function.  It was added so you can get the GMT
timestamp on the server side.  Not the local side which the JavaScript
function provides.

Which brings up a very important point.   Using Javascript is another way to
do this of this related work, in both GMT and in the non-GMT local side
(browser) time reference.

Just remember this very important distinction:

                Client vs Server-Side Scripting.

JavaScript is run on the browser (Client Side Scripting), after the WEB
Server sends the page.

WCT is run on the web server (Server Side Scripting) as the server reads,
processes, and generates the page from the template and pushes the final
output to the browser.


<CHRIS CRANFORD> wrote in message
news:1110530484.33.1110267990@winserver.com...
> -> This is a follow up to announce the next pending update (AUP 451.4)
will now
> -> support new DATE.XXXX sub values for the WCT DATE macro:
>
> -> New DATE sub value macros
>
> ->     DATE.YEAR
> ->     DATE.MONTH
> ->     DATE.DAY
> ->     DATE.HOUR
> ->     DATE.MINUTE
> ->     DATE.SECOND
> ->     DATE.MILLISECONDS
> ->     DATE.DAYNUMBER         # of days since 1970
> ->     DATE.TIMENUMBER        # of seconds in the current day
> ->     DATE.DAYOFWEEK        Sun=0, Mon=1,,, SAT=6
>
> Hey man, these are great to now have.  Just saw the post and wanted to
> comment.  I know we had some discussion in the past about timezone.
> Since the date macro is returning date and time elements, would it be
> helpful to have it return the timezone abbreviation in some manor such
> as either 'EST' or 'EDT' too ??   Just a thought.  I know you are
> planning to release this to pre-gamma monday.  Just wanted to put this
> on the plate for a future consideration if so.
>
> Thanks
> Chris
--- Platinum Xpress/Win/WINServer v3.1
 * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)

.