Re: Parsing RFC2231 or newer spec'd data

2023-05-03 Thread Oleg Kalnichevski
On Tue, 2023-05-02 at 17:16 +, Gary D. Gregory wrote: > On 2023/05/01 21:19:35 Michael Osipov wrote: > > Am 2023-05-01 um 22:46 schrieb Gary Gregory: > > > Well, that puts a nail in that coffin. Thank you for the details. > > > > BUT, you have to look into Apache James which has a decent MIME

Re: Parsing RFC2231 or newer spec'd data

2023-05-02 Thread Gary D. Gregory
On 2023/05/01 21:19:35 Michael Osipov wrote: > Am 2023-05-01 um 22:46 schrieb Gary Gregory: > > Well, that puts a nail in that coffin. Thank you for the details. > > BUT, you have to look into Apache James which has a decent MIME parser > which we are using at work. I would say that it is enough

Re: Parsing RFC2231 or newer spec'd data

2023-05-01 Thread Michael Osipov
Am 2023-05-01 um 22:46 schrieb Gary Gregory: Well, that puts a nail in that coffin. Thank you for the details. BUT, you have to look into Apache James which has a decent MIME parser which we are using at work. I would say that it is enough to have one decent lib in ASF land than multiple medi

Re: Parsing RFC2231 or newer spec'd data

2023-05-01 Thread Gary Gregory
Well, that puts a nail in that coffin. Thank you for the details. Gary On Mon, May 1, 2023, 16:19 Michael Osipov wrote: > Am 2023-05-01 um 22:14 schrieb Gary D. Gregory: > > Hi All, > > > > Over at Apache Commons FileUpload, I am helping to rework the code base > for our upcoming 2.0 release.

Re: Parsing RFC2231 or newer spec'd data

2023-05-01 Thread Michael Osipov
Am 2023-05-01 um 22:14 schrieb Gary D. Gregory: Hi All, Over at Apache Commons FileUpload, I am helping to rework the code base for our upcoming 2.0 release. We have a whole package [1] of gnarly HTTP-related parsing for RFC2231 which I was hoping to replace with a dependency HC. (I want HC t

Parsing RFC2231 or newer spec'd data

2023-05-01 Thread Gary D. Gregory
Hi All, Over at Apache Commons FileUpload, I am helping to rework the code base for our upcoming 2.0 release. We have a whole package [1] of gnarly HTTP-related parsing for RFC2231 which I was hoping to replace with a dependency HC. (I want HC to be the reference for all things HTTP.) I see tha