# Design Pattern for Recurring Events

**URL:** <https://www.ruby-forum.com/t/design-pattern-for-recurring-events/141216>\
**Category:** Rails\
**Created:** [June 23, 2008, 7:01pm UTC](https://www.ruby-forum.com/t/design-pattern-for-recurring-events/141216 "2008-06-23T19:01:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdaoust](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/dbc845/32.png) [@mdaoust](https://www.ruby-forum.com/u/mdaoust)\
**Post date:** [June 23, 2008, 7:01pm UTC](https://www.ruby-forum.com/t/design-pattern-for-recurring-events/141216/1 "2008-06-23T19:01:26Z")

</div>

Not specifically a rails question, so forgive me…

How would people recommend representing recurring events in a rails  
application? Are there any established design patterns?

~ Mark

---

<div class="post-metadata">

**Author:** ![mdaoust](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/dbc845/32.png) [@mdaoust](https://www.ruby-forum.com/u/mdaoust)\
**Post date:** [June 23, 2008, 9:12pm UTC](https://www.ruby-forum.com/t/design-pattern-for-recurring-events/141216/2 "2008-06-23T21:12:12Z")

</div>

Posted on June 14th on this very list: [http://runt.rubyforge.org/](http://runt.rubyforge.org/)

On 23 Jun 2008, at 19:01, Mark D. wrote:

> Not specifically a rails question, so forgive me…
> 
> How would people recommend representing recurring events in a rails  
> application? Are there any established design patterns?

Best regards

Peter De Berdt