google1@[EMAIL PROTECTED]
writes:
> On Jul 22, 6:01 am, Ludovic Brenta wrote:
>> Wow, this looks quite professional! Are you planning to merge your
>> library into AdaCore's Ada Web Server (http://libre.adacore.com/aws),
>> which already includes an SMTP client and server but apparently lacks
>> the powerful mail handling capabilities of your library?
>
> Hi Ludovic.
>
> I hadn't considered merging with AWS. It seems mostly focused on RFC
> 2821 (SMTP) and you actually wouldn't need MIME in an RFC 2821 MTA,
> nor would you need SMTP in an MUA (or anything designed to run as a
> client to an MTA like a mailing list server). Where Basil could
> complement AWS is with its RFC 2822 structured header parsers, which
> an MTA would need.
>
> Probably the best way to do it would be to make a glue package that
> can translate AWS header objects into Basil header objects, so you can
> use the structured header parsers, and then back again. I don't think
> that would be very difficult and I could probably get that in the next
> release.
If you're planning to use AWS's SMTP client code, it looks like you're
going to need this glue for your mailing list server anyway.
The reason I wasn asking is not because I was interested in using your
library; only because I think it is nice in general to consolidate
small but related libraries into larger ones, or at least host them in
common places, so that users can find them more easily. Another
benefit is to avoid inconsistencies and incompatilibities between
libraries, so that a single program can use several libraries
simultaneously. And, of course, to reduce duplication of work.
Speaking of which, is there a good reason why Basil needs its own
"header objects" different from AWS's "header objects"?
--
Ludovic Brenta.
|
