[Mono-list] AppServer code is posted
Sun, 12 Jan 2003 20:27:45 -0500
Thanks for your thoughts and explaination of the MS licensing. The code is
structured to host various kinds of applications (each is essentially a
plug-in). One of those applications is "web". When I started this project,
the XSP server was not yet available...and Cassini was a good starting
This afternoon I took a snapshot of the XSP server and created a new
XSPApplication plug-in which can be a replacement for the Cassini-based
application host. So, if distributing the MS code is a problem, I can make
it a seperate download. The download would include a lightweight wrapper +
the MS code. Does this sound like a good solution?
Thanks for your comments,
>From: "Steven Balthazor" <email@example.com>
>To: "'Brian Ritchie'" <firstname.lastname@example.org>
>Subject: RE: [Mono-list] AppServer code is posted
>Date: Sun, 12 Jan 2003 14:57:14 -0700
>I hope this is more along the lines of advice and guidance. This is my
>on the licensing issues involved. I don't wish to intentionally provide
>opinions about the "goodness" or "badness" of the licenses involved, just
>understanding of how the issues apply in this case. I am not a lawyer just
>developer who has read many license agreements; so I am interested to hear
>what others may say about this issue.
>I havenít looked at the Appserver source code yet to see what you have
>redistributed (and as you will see later in my discussion even if I did
>at your source code, only you may know what can be redistributed); however,
>I did take a look at the Cassini stuff as well as some other "free"
>Microsoft software a couple of weeks ago when I last looked at your app
>server (basically because you referenced it in your site).
>I downloaded and installed the Cassini server; the EULA which is used to
>"click-wrap" the software (i.e. you can't install it until you agree to it)
>is attached. Read it carefully; especially section 2.2; I like to refer to
>this as the Microsoft Anti-Open-Source License agreement. Basically you
>use their code for your own purposes, and can even re-distribute it inside
>your own product (even sell your product) as long as you don't redistribute
>your product as open source software (they don't say it directly, but that
>is my interpretation of their legalese--read the last part of paragraph
>If your intention is to use the Cassini server temporarily to create other
>functionality and then later plug in some other open source product (mono
>something else) to take the place of the Cassini server then your code can
>remain open sourced; as long as your code does not directly include any of
>the Cassini code; however you are not able to redistribute any components
>the Cassini server (you could however provide a link to the Cassini server
>for those who wish to try your functionality).
>You have to be very careful to keep from infringing on Microsoft's
>most open source projects are very good about identifying each source file
>as being covered by the appropriate open source license; Microsoft just
>includes the clause:
>† Copyright (C) Microsoft Corporation.† All rights reserved.
> THIS CODE AND INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
> KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
> IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
> PARTICULAR PURPOSE.
>However the click wrap agreement that you agreed to when you first
>the software is truly the defining agreement.
>It would appear that microsoft uses a similar license agreement on all of
>its "ASP.Net Source Projects" on www.asp.net; so anyone looking to use
>projects (http://www.asp.net/Default.aspx?tabindex=7&tabid=41) should be
>aware of the restrictions.
><< cassini_eula.txt >>
The new MSN 8 is here: Try it free* for 2 months