I think complexity should only be limited by the contributors time and ability to document a mailet's features. :)
I think it'd be better to roll Oki's changes into the existing Forward mailet (or whatever mailet it's closest too... seems like it's a lot like NotifySender/NotifyPostmaster). Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ ----- Original Message ----- From: "Danny Angus" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 16, 2001 3:21 PM Subject: Another question.. > > Oki's ForwardAsAttachment mailet also made me wonder, > Should we be building big configurable mailets, > > [so say Oki's attachment stuff was in Forward and it would only be used if > configured to, > and Forward might also contain code forward a copy without ghosting the > original etc etc.] > > Or, should we be keeping Mailets small and simple, so we have two or three > seperate ForwardXxx classes for slightly different tasks. > > I only ask 'cos the mailets in the dist. will be bound to be used as > reference examples and I wondered what anyones views of the pros and cons > were. > > d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
