>Ye have done a great job in creating this product, >and I send
>my congratulations.
Bruce is the "chief". He has done the core stuff before I have get involved! Send your congratulations
to him!
Speaking of content type I think the best solution would be including new property of PipelineDocument. In case we know extension we could guess mime type. In case we generate document we do know mime type (xml or txt). In case we use message content (SmtpWriter) we also know content type.
Other solution would be to have contentType config option in SmtpPipelineStage.
I prefer first solution.
>I think I would like to get involved in the Babeldoc >project, but it will be a number of weeks before I ?>am in a position to do that.
You are already helping us!
Best regards,
Dejan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>Ye have done a great job in creating this product, >and I send
>my congratulations.
Bruce is the "chief". He has done the core stuff before I have get involved! Send your congratulations
to him!
Speaking of content type I think the best solution would be including new property of PipelineDocument. In case we know extension we could guess mime type. In case we generate document we do know mime type (xml or txt). In case we use message content (SmtpWriter) we also know content type.
Other solution would be to have contentType config option in SmtpPipelineStage.
I prefer first solution.
>I think I would like to get involved in the Babeldoc >project, but it will be a number of weeks before I ?>am in a position to do that.
You are already helping us!
Best regards,
Dejan