Swerve, Thanks - glad to see someone saw the same analogy and a bit of irony regarding this issue. Everyone else seemed to think they had to respond with the proper definition of a time zone...
Why not stick the outage into your database in UTC time, then rip your OpenSRS Live Reseller Updates out accordingly, with each reseller getting the outage in his own time zone... As someone mentioned, "It's not rocket science." I am the world's worst Perl programmer - OK, maybe there are a few worse - but even I know how to convert time zones... Sorry I brought it up. -- John Keegan [EMAIL PROTECTED] http://RackShare.com > From: Swerve <[EMAIL PROTECTED]> > Date: Wed, 04 Dec 2002 08:39:43 -0500 > To: Dave Warren <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > Subject: Re: OpenSRS Live Reseller Update - 11/29/02 > > Oh, that's too many, Mr. Devils Playground. > > Having an asterisk beside the announced time and a list of 6-8 major cities > and their respective times at the end of the email won't break the bandwidth > and might even be an interesting aesthetic reflecting the large geographical > range of the folks here. > > Kind of when you walk into a hotel that has 6 different clocks reflecting a > wide range of their customers. > > Swerve > > "Get thee > back into the tempest..."
