Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Jeff Charette <iomatix@yahoo.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_26EAC803-0C68-4FFA-9C5F-327F67E1ABCE"
Message-Id: <E952B3AE-3F34-4FB0-AD01-2A90ACFCE5E2@yahoo.com>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: map timezones
Date: Thu, 7 Mar 2013 12:21:35 -0500
References: 
 <CAHGcXejH1N2=R98qBQ2nXz4kq5+q0RNFghcBv1odm_GNoWskpQ@mail.gmail.com>
To: user@couchdb.apache.org
In-Reply-To: 
 <CAHGcXejH1N2=R98qBQ2nXz4kq5+q0RNFghcBv1odm_GNoWskpQ@mail.gmail.com>

--Apple-Mail=_26EAC803-0C68-4FFA-9C5F-327F67E1ABCE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Kanso has the moment.js library as well so you can require it client and =
server side.
http://kan.so/packages/details/moment/1.7.2-kanso.2

Jeff Charette | Principal=20
We Are Charette
web / identity / packaging

m  415.298.2707
w  wearecharette.com
e   jeffrey@wearecharette.com

On Mar 7, 2013, at 12:24 AM, Will Heger <will.heger@gmail.com> wrote:

> @Jens
>=20
>> What=92s =93local time=94? The time zone of the server? A map/reduce =
function
>> has to be a =93pure=94 function, so it can=92t depend on any external =
inputs
>> that might change, such as the current timezone.
>=20
>=20
> Well, this was very much my point.  I'm not interested in server =
locale or
> a Date() time, I'm interested in the absolute time stamped on my docs =
by
> clients.  I just want to use it in conjunction with location so my =
maps can
> report local time.
>=20
> We are missing the following library for our views:
> https://github.com/mde/timezone-js
>=20
> In that way, as a developer I can store times within my document using
> either UTC or epoch times.  These times could be current or =
historical, it
> doesn't matter.  What matters is that they're unambiguous. And there =
exists
> a pure function F such that:
> F(doc.epoch_time, doc.location) =3D A time for that locale for that =
moment
> in history
>=20
> Absent this, I think the best idea is to store the epoch time and =
force the
> client to also stamp the relevant local UTC offset.  It offers the =
most
> flexibility in terms of reporting, deals with DST weirdness, and I =
have
> more resources to look-up UTC offsets from client code than in couch.
>=20
> Thanks for letting me rubber duck this, I hope this strategy helps =
someone
> else,
> -Will


--Apple-Mail=_26EAC803-0C68-4FFA-9C5F-327F67E1ABCE--