I'm a bit toasted, be warned :] I'm thinking the message/contact object is pretty simple, just the content, the date info, and a person (and maybe contact method, if specified).
Use that info to grab the person, or maybe tell something to use the person, to send a communique using the preferred/default contact method, if a specific one isn't specified? Something like that. Depends on what all you want to do... hit up groups of people, for instance? Do you need to care about what kind of mechanism is used to contact the person? Are you going to validate what contact methods are available for the person (where/when might be a better question)? Guess it depends on if you're thinking of the types of contacts as objects, or the ways of contacting people as means for objects, if that makes sense? There's 6 million or so ways to do anything, but I like the idea of being flexible, having things knowing how to get to things, vs. actually having the things, if that makes sense... ok, I've said that twice, guess that's it. Getting a little too specific for myself. =] I'll end it here with a comment on the UML, saying "people to phones to companies to emails and whatnot are one of the most-used examples, google will probably turn up 50 ways to do what you want- but the best? Ha!". Thinking about all the UML types will help tho (not just class diagrams and whatnot, but those other, more abstract ones, that seem like a waste of time almost because they don't really do much, sorta, until you realize they help you think about the process from a different perspective, kinda :-]p). This was probably close to unhelpful, but I thought I'd take a stab, and wanted to say something different than blah blah "is a" and "has a"... =) HIH -- No one would choose a friendless existence on condition of having all the other things in the world. Aristotle On Wed, Nov 12, 2008 at 9:54 PM, Judah McAuley wrote: > > This brings up an issue of how to use the data I'm returning. > > lets keep it simple and say that a Contact has properties of id, > notifydate, userid, contactmethod and PhoneContact has id, contactid, > phonenumber, message and EmailContact has id, contactid, toaddress, > subject, body > > My first thought is that I get grab a Contact and get back a structure > like this: > > id > notifydate > userid > contactmethod > content(obj) ---> id, toaddress, subject, body (if email) OR id, > phonenumber, message (if phone) > > In that scenario, every contact I get back will look the same. A > notifydate, the person to notify, the method and then an object with > the contents of the contact to be made. > > It sounds like you are suggesting though is that > getAbstractContact(103) would return a different looking object > depending on if that particular contact was of type phone or email, > correct? > > Thanks, > Judah > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
