NYCPHP Meetup

[cliff]

> >>basic data structure for websites. For example, given an event data
> >>construct (what, when,where,whom,about/related to, comments about, etc)
> >>one could build many common MVC websites.
> >>    
> >Some observations:
> >"When" is typically two values, start and end. To find the events in a
> >given month, you look up all the events that start and/or end within
> >the month, or that start before and end after the month.
> >
> >But... recurring events are a difficult problem with this model. You
> >can insert all the instances of a recurring event for the next 5
> >years, and group them together so they can be changed as a group. It
> >is not so difficult to imagine a situation where that gets really
> >ugly.
> >  
> >
> Actually, isn't "when" really just one value - offset from defined 
> zero? "duration" is a second attribute of the event.  And daylight 

And isn't recurring just a flag? The presentation or business layer can see if a recurring event falls into a 
calendar timframe by doing some simple math.