The other day, I blogged about XStandard and weird caching issues. I think that I was wrong in my diagnosis. During all of this I had debugging turned on in my XStandard ColdFusion web services. In my debugging, it writes the SOAP request and response headers to htm files in a special debug folder. It basically does a CFDump on the XML object created for the SOAP communication. On large responses (the list of files in a large directory), the CFDump was creating a file that was close to a megabyte in size. Somehow, this was making the system crap out.
When I turned off debugging in the web services (a setting in the configuration file), not only does the XStandard editor run faster, but no more crapping out. Sweet!
Looking For A New Job?
- Mobile Application Developer at Xorbia Tickets
- 7 Year + Lead ColdFusion Developer at Atprime Media Services
- Full Time ColdFusion Developer Needed at InterCoastal Net Designs
- Developer-focused job platform at Honeypot