[Mono-list] Re: Contributing non .NET libraries

Gaurav Vaish gvaish@iitk.ac.in
Wed, 13 Feb 2002 10:22:10 +0530

----- Original Message -----
From: "Miguel de Icaza" <miguel@ximian.com>
To: "Greg Pasquariello" <gpasq@theoreality.com>
Cc: <mono-list@ximian.com>
Sent: Wednesday, February 13, 2002 05:36
Subject: [Mono-list] Re: Contributing non .NET libraries

: Very nice!  I would like to know more about this.  It seems like this is
: complementary to the work that Gaurav was proposing.  .NETMail seems to
: be a transport/delivery mechanism, while Gaurav's is more of a Mime/RFC
: framework for creating/extracting these messages.

    That's right.
    Till now, I have been able to work around with only API for the Messaging
part. Still not touched Transport and Store part. It would be very nice if we
could work in complement, unless of course we've already developed any of the
parts independently. Would like to go through any coding that you may have done
and/or any architecture that has been designed / in process of designing. That
will help interfacing the various components.

: As I suggested Gaurav, for any code that is not part of the Microsoft
: API, we should create extra assemblies.  It is perfectly fine if our
: assemblies do depend on the extra ones.

    I think, that is going to be the criterion now. So, we may be have assembly
named Mono.Mail if we have Mail in a separate assembly. Miguel may be relieved
off thinking of a name ;-)
    If we combine the Web-server efforts with this, we may have something like
Mono.Internet - sounds crazy?

Gaurav Vaish

: Check:
: http://www.go-mono.com/ccvs.html
: For details on getting your CVS account.
: Miguel