in reply to Should I extract Mail::Sender's debuging into a separate module?

Hi Jenda,
I'm working with your module. It's great work. I take off one's hat (joking apart).
About your question, I'd like suggest to do a debug more compact. Because all data are written in thins log, including a content of attachment file. It makes the log file huge and it needs processing of debug data if I, for example, want to redirect this data into Apache log or log of my application.
But, I think, that useful debug information is the information which consists only reply of mail server, without any attachments.
      
--------------------------------
SV* sv_bless(SV* sv, HV* stash);
  • Comment on Re: Should I extract Mail::Sender's debuging into a separate module?

Replies are listed 'Best First'.
Re: Re: Should I extract Mail::Sender's debuging into a separate module?
by Jenda (Abbot) on May 27, 2003 at 16:34 UTC

    Well I assumed the debug will only be used for debuging, instead of being logged in production. But I guess you are right, I should optionaly turn the logging off for the mail body&attachments to make the debug file smaller. I think the best solution would be to define four or five debug levels:

    • no logging
    • only conversation, not the mail data
    • conversation and mail message headers
    • conversation and mail message and part headers
    • all
    Thanks for your idea.

    Update: You may find a beta version with this implemented at http://jenda.krynicky.cz/Beta/Sender.pm let me know if this works the way you need. See the debug_level option.

    Jenda
    Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
       -- Rick Osborne

    Edit by castaway: Closed small tag in signature

[reply]
      I think, It's good idea to do several debug levels. I will try to use a beta version of your module.
      Thank you very much! 
            
--------------------------------
SV* sv_bless(SV* sv, HV* stash);
[reply]

In Section Meditations