Re: feature request-- [epoch]

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 55515
interpreted = N
texte = Sorry ahead of time if my thinking is malformed (this IS off the top of my head...), but intuitively, it seems to me that by knowing the date of the epoch ('standard' (UNIX, etc.), or your own) you could do anything you want... [text multi=T]epoch_day=10/16/1973;epoch_time=16:00:00[/text] <-- my birthday, heheh First of all, we know that there are 86400 seconds in a day, and therefore 86400 unique IDs every day. Next, we know that there are 365 days in a year, and an extra day in leap years. I assume that WebDNA's date math accommodates leap years, so I am going to trust that for now. Ok, now that said if 4pm on Oct 16th, 1973 = 0, which is the epoch here, then we can make all sorts of deductions and assumptions to figure out/convert what we need, on the fly, at any given time, so therefore, Oct. 17th, at 4pm, then would = 86400 (24 hours later), and so on. True, this number will grow exponentially, and I suppose that ultimately would be a problem, but I'll assume, again, that WebDNA can/will accommodate this somehow (I mean 10000000000000000000000000000000000000000000000000000 X 40000000000000000000000000000000000000000000000000000 is really just 1x4 with a buttload of zeros after it...) Now, to get the ID for this very second, then, in theory, it seems relatively easy enough to find out how many days have passed since [epoch_date] and multiply that by 86400, then calculate the number of seconds since [epoch_time] (in this case, 4pm yesterday) and add those 2 results together. ? -Dan ------------------------------------------------------------ http://www.StrongGraphicDesign.com http://www.SearchBoise.com ------------------------------------------------------------ On Fri, 16 Jan 2004 09:08:09 -0600 Donovan Brooke wrote: >Hello, >Can I suggest again the ability to specify the epoch. > >[math epoch=mm/dd/yyyy]{[date]}[/math] >[format days_to_date&epoch=mm/dd/yyyy][thenum][/format] > >[!] unix has a different epoch and there will be times >were we will have to grab (maybe even via XML) values from >other systems [/!] > >Also I will use this time to ask for "seconds since epoch" >once more. ;-) > >Thanks, >Donovan > >-- > =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o > DONOVAN D. BROOKE Eucalyptus Design > <-Web Development (specializing in eCommerce), -> > <-Graphic Design, and Pre-Press Consultation -> > > ADDRESS:> Donovan Brooke > DBA Eucalyptus Design > N2862 Summerville Park Rd. > Lodi, WI 53555 > PH:> 1.608.592.3567 > Web:> http://www.euca.us > =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o > > >------------------------------------------------------------- >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: feature request-- [epoch] ( John Peacock 2004)
  2. Re: feature request-- [epoch] ( Donovan Brooke 2004)
  3. Re: feature request-- [epoch] ( Donovan Brooke 2004)
  4. Re: feature request-- [epoch] ( "Dan Strong" 2004)
  5. Re: feature request-- [epoch] ( John Peacock 2004)
  6. Re: feature request-- [epoch] ( "Dan Strong" 2004)
  7. Re: feature request-- [epoch] ( "Nitai @ ComputerOil" 2004)
  8. Re: feature request-- [epoch] ( John Peacock 2004)
  9. Re: feature request-- [epoch] ( Donovan Brooke 2004)
  10. Re: feature request-- [epoch] ( "Nitai @ ComputerOil" 2004)
  11. Re: feature request-- [epoch] ( Donovan Brooke 2004)
  12. feature request-- [epoch] ( Donovan Brooke 2004)
Sorry ahead of time if my thinking is malformed (this IS off the top of my head...), but intuitively, it seems to me that by knowing the date of the epoch ('standard' (UNIX, etc.), or your own) you could do anything you want... [text multi=T]epoch_day=10/16/1973;epoch_time=16:00:00[/text] <-- my birthday, heheh First of all, we know that there are 86400 seconds in a day, and therefore 86400 unique IDs every day. Next, we know that there are 365 days in a year, and an extra day in leap years. I assume that WebDNA's date math accommodates leap years, so I am going to trust that for now. Ok, now that said if 4pm on Oct 16th, 1973 = 0, which is the epoch here, then we can make all sorts of deductions and assumptions to figure out/convert what we need, on the fly, at any given time, so therefore, Oct. 17th, at 4pm, then would = 86400 (24 hours later), and so on. True, this number will grow exponentially, and I suppose that ultimately would be a problem, but I'll assume, again, that WebDNA can/will accommodate this somehow (I mean 10000000000000000000000000000000000000000000000000000 X 40000000000000000000000000000000000000000000000000000 is really just 1x4 with a buttload of zeros after it...) Now, to get the ID for this very second, then, in theory, it seems relatively easy enough to find out how many days have passed since [epoch_date] and multiply that by 86400, then calculate the number of seconds since [epoch_time] (in this case, 4pm yesterday) and add those 2 results together. ? -Dan ------------------------------------------------------------ http://www.StrongGraphicDesign.com http://www.SearchBoise.com ------------------------------------------------------------ On Fri, 16 Jan 2004 09:08:09 -0600 Donovan Brooke wrote: >Hello, >Can I suggest again the ability to specify the epoch. > >[math epoch=mm/dd/yyyy]{[date]}[/math] >[format days_to_date&epoch=mm/dd/yyyy][thenum][/format] > >[!] unix has a different epoch and there will be times >were we will have to grab (maybe even via XML) values from >other systems [/!] > >Also I will use this time to ask for "seconds since epoch" >once more. ;-) > >Thanks, >Donovan > >-- > =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o > DONOVAN D. BROOKE Eucalyptus Design > <-Web Development (specializing in eCommerce), -> > <-Graphic Design, and Pre-Press Consultation -> > > ADDRESS:> Donovan Brooke > DBA Eucalyptus Design > N2862 Summerville Park Rd. > Lodi, WI 53555 > PH:> 1.608.592.3567 > Web:> http://www.euca.us > =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o > > >------------------------------------------------------------- >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ "Dan Strong"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Wireless WebDNA available today! (2000) Nested search (1997) [ListFiles] Within [LineItems] (2001) Is this possible, WebCat2.0 and checkboxes (1997) Bug Report, maybe (1997) WML (2000) Re:Gil's in the lead (1999) [NT] ie 4.0 required (1997) Field name-subcategory (1997) WCS Newbie question (1997) 'page impression' techniques for banner ads (1999) Smith Micro - no competition (2000) shoppingcart reload qty (1997) Web Catalog vs. ICAT (1997) Progress !! WAS: Trouble with formula.db (1997) 'does not contain' operator needed ... (1997) Emailer (1997) [SearchString] problem with [search] context (1997) pictures / referrer etc. (1998) Close-to Comparison Code (1998)