On Saturday, 19 April 2014 16:17:57 UTC+2, Parsifal wrote: > > (...) But as about a standalone list of banned emails that has no > association with any other entity, it's a bit difficult for me how I can > think about it as object! > What is the *use case*?
Don't answer here, it's your process, just for yourself, but to give you an idea of how this list can be associated with the rest of the system, some general modeling questions I would pose, off the top of my head: Who puts the banned email addresses on that list? Why? What is done with it? Where is it applied? How? What is its function? Is it some extra feature in order to keep the system free of spam? Or is it an essential part of the domain-language? In what parts of your model (bounded contexts) is it used? Do they expire? Do you only have banned email-addresses or also banned IP-addresses? Do you keep a log of why and when they were added? Is it part of some general authentication policy? What are the benefits of keeping those addresses and what are the costs? How often are they used? When are they modified? How many do you expect? What external services could be used instead? What other lists of e-mailaddresses do you keep? Would a whitelist be more effective than a blacklist? Or a combination? Are there other "rules" than banned email addresses? Rule, for whom, where, when, why, what, how? Etc. -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
