On Jul 19, 2006, at 2:58 PM, Daniel Henninger wrote: > > Aside from "that shouldn't happen"? ;) Does running it with the - > D option help identify what's going on any? (it being PyAIMt)
Sorry, missed a bit. I have run pyAIMt with the -D option, but the debugging output it gave me was (a) *very* verbose, and (b) not useful (for me) in figuring out what was going on. As I mentioned in the other email (URL to archives posted in previous message), I instrumented pyAIMt as described to see the incoming and outgoing xml stream. However, I've come to suspect that I only got most of the communications, and not all (and I forget at the moment what it was that made me suspicious of this -- something to do with seeing arrivals at my instrumented component which didn't correspond exactly with transmissions from the pyAIMt component). -- Matt Anderson
