From: Christian R. <lil...@ce...> - 2002-10-08 10:45:09
|
Allen, This has been corrected in the docs. The time is indeed UTC, and it was only my personal foolishness which resulted in the incorrect docs. The updated docs will be published later today. christian > User: [#121] prisoner > MOO: 1.8.1+g1+s > Core: lily running rev 2.6.2 > Server Time: Sun Aug 11 11:06:10 2002 EDT > ---%report%---- > The SLCP documenation at > http://lilycore.sourceforge.net/Simple%20lily%20Client%20Protocol.html > says > unix_time is the Unix-style time on the server, > <em>in the local timezone!</em> > which contradicts this conversation on lily > ### It is now Sat Aug 10, 2002 ### > > -> (00:09) From (), to lily-dev: > - The time sent from the lily-server is not UTC, it's lily-server time sent > - from the Jan 1st 1970 00:00 local lily server time? > > -> (00:11) From Kazrak, to lily-dev: > - In SLCP, the time sent is a Unix time_t, which is UTC-based. > > -> (00:11) From (), to lily-dev: > - So you see the timezone in AZ not NY? > > -> (00:12) From Kazrak, to lily-dev: > - Correct. It's up to the client to handle it intelligently. (Which is, > - fortunately, fairly easy to do.) > > -> (00:12) From (), to lily-dev: > - Yeah... if it's in UTC, it is ;) > > -> (00:13) From Kazrak, to lily-dev: > - In tlily's case, it just hands the timestamp to localtime(), I believe. > - I'd assume most clients do the equivalent in their languages' libraries. > > -> (00:14) From (), to lily-dev: > - cool :) > > Please clarify. > > > ---%report%---- > > |