<snip>
> I'll BE the guinea pig.. No problem! But I need the total
> responsiveness from MM to make it work. And I'm completely willing to
> share my experiences and solutions with the CF community, so that they
> can benefit from it.
>
> But.. (And there's ALWAYS a BIG BUT(T) somewhere! <grin>) Don't ask me
> for a credit card to do this.
<snip>
If we cannot reproduce this in house, we cannot fix it. If it is not escalated
through support, the likelihood of the problem getting addressed is negligible.
We can do comparisons all day long, however what it boils down to is this:
You and anyone else seeing this problem, need to contact technical support.
You need to allow them to get the information they need to point you to a solution.
Yes, other people may have seen this problem, but so far, as far as I can tell, the
problem seems like "CF Dies under load".
Well, we ran CFMX under load, for *weeks* before we shipped it. I know; I had
to help out with it.
We have supplied a clearly defined avenue to getting your issues heard. The
avenue is supported and maintained by Macromedia (ie: not a 3rd party mailing list, or
a website) and this is the most efficient method of issue resolution we have at the
moment.
Is it perfect or foolproof? Is it final? No. Are we examining it and looking
for ways of improving it? Yes.
Right now however, that is the *best* method of getting an issue resolved.
-Jesse
>
>
> | -----Original Message-----
> | From: Scott Brader [mailto:[EMAIL PROTECTED]]
> | Sent: Tuesday, October 08, 2002 7:28 AM
> | To: CF-Talk
> | Subject: RE: LONG time CF Supporter - About ready to dump CF!
> |
> |
> | Before anyone else comments, yes, this probably should be a
> | cf-community topic now.
> |
> | Jesse,
> | I certainly see your point, however, as a developer and small
> | business owner, there are financial concerns that a large
> | organization like MM wouldn't understand. My business
> | _depends_ on my customers being able to trust what I tell
> | them. If I recommend a change to their
> | hardware/software/processes/etc. and they implement it, my
> | reputation is on the line. In that light, I am always _very_
> | hesitant to recommend production software upgrades until they
> | have been through the wringer a while.
> |
> | My other problem is that, to report a possible bug, many
> | software companies expect you to essentially "put down a
> | deposit" before they will take your call. I, for one, simply
> | cannot afford to gamble that tech support is going to agree
> | that my issues are bugs until they get a lot of reports of
> | it. That is a financial risk for small businesses that are
> | struggling to survive in these economic times.
> |
> | Maybe if the software companies (and I'm not saying MM
> | doesn't, because I simply haven't checked) provided an
> | efficient tool for reporting possible bugs without requiring
> | the normal full tech support call and deposit, people would
> | be more likely to civilly report the bugs than vent on the forums.
> |
> | Thanks,
> | Scott
> |
> | Scott Brader
> | Prairie Software Development LLC
> | 101 East Sadd Street
> | PO Box 235
> | North Prairie, WI 53153-0235
> |
> | Phone: 262.392.9173
> | Fax: 262.392.9174
> |
> | Toll Free: 888.821.3427
> | Mobile: 262.490.1376
> |
> <http://www.prairiesoftdev.com>
>
> Amateurs practice until they get it right,
> Experts practice until they can't get it wrong.
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Get the mailserver that powers this list at http://www.coolfusion.com
