[Mono-list] Mono as a Server Platform
Thu, 30 May 2002 14:54:37 -0700
That chunk of 'System.Reflection.*' things at the top of each
class-status page are missing attributes (as indicated by the red cross
and the ''s). They are assembly-level attributes that are 'attributed'
in the Microsoft DLL but are missing in the Mono version.
The System.Reflection attributes themselves are defined in the 'corlib'
assembly, but they're not listed in corlib's class-status page under the
System.Reflection namespace because they are themselves complete.
From: code [mailto:firstname.lastname@example.org]
Sent: Thursday, May 30, 2002 7:54 AM
Subject: RE: [Mono-list] Mono as a Server Platform
In fact, I am little confused by the Class status page on mono web site.
For every class portion(e.g. System.Data, System.XML),
System.Reflection.* is always listed there, I don't know why place them
I think it's more pratical to take mono as a Linux Server Platform, then
try to expand it to desktop. I have heard several companies that want to
use mono as its server side platform, and take Windows .NET as client
side platform(for C/S application).
> -----Original Message-----
> From: Rodrigo Moya [mailto:email@example.com]
> Sent: Thursday, May 30, 2002 10:28 PM
> To: code
> Cc: Mono List
> Subject: Re: [Mono-list] Mono as a Server Platform
> On Thu, 2002-05-30 at 07:21, code wrote:
> > Hi, all,
> > Could anyone tell me how far mono is to be a server
> platform? It need
> > not to have GUI, but database support, network, remoting services,
> > XML, and other stuff required by a server platform. I don't
> know if I
> > could use it now, or have to wait for several month, or a year?
> database support is almost there
Mono-list maillist - Monofirstname.lastname@example.org