Folks Sorting out the support for multipart coded requests is the next item on my to-do list.
I am going to approach James developers and ask them if they would be interested in having our multipart encoder contributed to Mime4J. It may well be they would not, given Mime4j's rather strong emphasis on the decoding (parsing) side of things. What should be our fallback option? Migrating old code to HttpClient 4 codeline? Dropping multipart support altogether? Thoughts? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
