2
Vote

SwaEncoder is not thread safe?

description

As per description, since your storing the MimeContent and MimeAttachment within the SwaEncoder, and instance of SwaEncoder is not a prototype for each invocation, the possibility of a collision exists for applications that do asynchronous calls without synchronizing or queuing
the calls.
 
What do you think? or am I missing some 'magically' handling by the service model when the SwaEncoder/Factory are instantiated (once)?
 
A solution might be to create the custom binder programmatically each time, rather than configuring it through your app.config?
 
Other notes:
  • Instead of using Memory Stream a FileStream/IOStream would of been nicer for larger objects?
  • Instead of using Byte[] in writing the message, an Stream would of been nicer way to handle it?

comments