And that's exactly to my point... When I ask a specific question, I only want answers that address that specific question.
If it turns out *to me* that the solution I'm considering is wrong, then it's up to me to change my mind. I don't take anyone's advice as unassailable. If we all did that, nothing new would ever be done. When I get ready to entertain alternative solutions, I'll ask for them. Until then, the only topic to respond to is "Anyone ever created their own email archive with CF?" And by that question I'm asking for people's experience, but only in the scope creating an email archive with CF, not quickly dismissing the approach as wrong or offering alternative solutions. If I wanted those answers, I would have asked, "Is it wrong or a waste of time to attempt to develop an email archive system with CF?" or "What are the alternative solutions to developing my own email archive system with CF?" Very specific questions. I just don't like it when people immediately try to hi-jack the thread based on their own experience and wisdom. For all I know, a CF solution has the potential to be perfect and those trying to dissuade me from that approach just didn't do it right and failed. I'm just hard-headed that way. But it's my post; people should stick close to the subject with replies and let *me* expand the scope if I want to. -----Original Message----- From: Cameron Childress [mailto:[email protected]] Sent: Thursday, April 18, 2013 11:00 AM To: cf-talk Subject: Re: Anyone ever created their own email archive with CF? On Thu, Apr 18, 2013 at 6:51 AM, Rick Faircloth wrote: > Thanks for NOT answering my question. I've gotten almost no helpful > information from this entire conversation, in spite of its tremendous > length. Rick - Please take this in the most constructive way possible. You asked a question, got a overwhelmingly consistant answer from the entire list that "you're doing it wrong". Now you are being somewhat unreasonably upset about that answer (considering you asked for input). You seem very fixated on a very very specific solution to a problem when you may be better served to have a wide open mind and listen to all opinions. Sometimes if everyone around you is saying "you're doing it wrong", then there is nothing more to it than just that. Often I talk to clients who start by telling me what they think the solution to their problem is. Sometimes it's a good solution, but often (usually due to their inexperience), it's not really the best solution for their problem. Instead I try to ask them to tell me their *problem*, not their *solution*. Until the client can let go of their preconceived notions of what *they* think the best solution is, we really aren't giving them the best work that we can. Take a step back and look at the question you were asking. You are prescribing a solution not presenting a problem. Many on the list are trying to stop you from making that mistake and moving you back to the actual problem you are trying to solve. Your root problem is one that most of the people on this list also have dealt with at some point. As a result, the overwhelming majority of people have told you how they solved that root problem, and why they chose that solution over the one you are suggesting. Now, you can (and are apparently) holding steadfast to your one single prescribed solution, and I wish you the best of luck with that. However, you have asked a community of peers for advice, and then aggressively (and rudely) rejected the overwhelmingly consistant advise of "you're doing it wrong". Good luck out there. -Cameron ... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:355492 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
