So you'd want to model that. Sounds like a user can have many messages. You need to think about how you model the details with messaging. Most common approach is to have a message domain object, but bear in mind that if you go that way, if recipient deletes message, the message should still exist as the sender may not have deleted it from their outbox. Generally a User sends-a message which has a sender-mailbox and a recipient-mailbox as well as a recipient.
You're going to want to think about business rules (how long messages can be kept), scaling issues and things like database indexes if you're looking to have a messaging based system for a large number of users. Did one recently for a site with a couple of million of members and it's non-trivial. We're actually looking to port the messaging piece from a clustered SQL db to a NoSQL key-value store with a Clojure or Scala RESTful service wrapping it (it was a JVM project). Best Wishes, Peter On Nov 3, 2010, at 1:14 PM, Mr Mody wrote: > thank you for feedback. I think action mailer is good, but I really need > to build a site with its own email or notice system. > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
