Posted by Jim Guerber on June 12, 2009 at 13:04:35:
In Reply to: Re: Comet 32 questions posted by Grant Foraker on June 12, 2009 at 12:51:25:
In Comet16 (current product), the internal error routine fills in common with all of the information it has about the user and the current environment, even though it makes no sense for the error in question. It then attempts to run qenditor.
There is much less info available in comet32, although more could be saved for this purpose. Depending upon the error, the file info, or the key info could or could not be relevant for example. I want a much smarter error processing. This could be done in an external program such as qenditor, or it could be done within the comet32 code itself.
There is also the issue of qerrlog. Maybe we should create it if it does not exist? I would also change its format. Maybe make it a text file, or a csv file?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.