I know didly squat about metacard, but here are my thoughts...
Raymond wrote:
>This sounds like a good idea. However, I do have a thought that it would
>indeed slow down the engine.
>
>This would require two things to work (at least). The software would have to
>keep track of everything going on. Just storing the call chain could require
>significant size (bloatware, anyone?). And unless you store the users'
>actions as well, you might not be able to figure out what went wrong anyway.
>The idea behind OOP is that you are programming objects to do their
>particular job when needed or called on. The code resides in the object. It
>isn't necessarily a smooth chain.
The call chain has to be stored already to take care of recursion.
>The second item would be that the user would have to be connected to the net
>and is willing for the software to transmit data to someone else (the
>developer). While this seems innocent enough for bug tracking, others might
>see a more sinister side. Real Networks has gotten a lot of flack over the
>revelation that its software reports back to it the listening habits of its
>users.
Perhaps the software should ask first, and provide a form to write a bug
report. That's how AOL Instant Messenger works, only in this case, we'll
appen the call chain and variables to the user's message.
>If it won't cause bloat or give the customer bad vibes knowing it is
>reporting its errors, I'd be willing to go for it. But we'd have to be
>careful.
>
>Raymond
