Hi Erik,
> 3).NET? Who knows what evil lurks in the heart of Microsoft?
If you are planning future development with .NET, then I suggest going with
Windows 2000 and IIS with your Witango Server. Although .NET can install on
NT - there are differences in memory management and some limitations of the
.NET Classes with NT. I can't recall what exactly, but I did read it
somewhere on MSDN.
As for .NET evil? This evil has the potential of creating a whole new
Enterprise level development war - between Java, .NET and everything else,
with Java and .NET dominating more than 80% of the market. In the new XML
Web Services war, Java and .NET are something like nearly 95% of the
market. (don't flame me - these numbers are not my fault :-}.)
Witango's new v6.0 Compiler technologies promises to convert your Witango
code into Java, and rumor has it that they are want to build a .NET version
too. There are happy days ahead for Witango developers :-)
Cheers....
----- Original Message -----
From: "Mark Bushaw" <[EMAIL PROTECTED]>
To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]>
Sent: Thursday, June 27, 2002 12:31 PM
Subject: Re: Witango-Talk: Windows OS Opinions
> My experience-
> 1) No problems upgrading from NT4 to W2K. But I had a fairly recent
setup without a lot of
> legacy apps. You may want to run Microsoft's hardware-checker first, to
identify any hardware
> that may need to be upgraded (video cards etc.)
> 2) IIS 5 is able to handle huge loads (Many tests show it outperforms
Apache, and even the ones
> that show Apache better, IIS 5 is very close.) WiTango 2K server may be
a bottle neck as it is
> not multi-threading.
> 3).NET? Who knows what evil lurks in the heart of Microsoft?
> 4) Upgrade to W2K server as soon as you can! It is so much faster,
easier, better than NT4.
>
> Mark Bushaw
>
> On 27 Jun 2002 at 10:58, Erik Kulvinskas wrote:
>
> > Hello,
> >
> > Currently I have a site hosted on a Windows NT 4.0 SP6+ machine using
Apache
> > as the webserver, mySQL as the DB and of course, WiTango as the App
Server.
> >
> > We are upgrading our client to a new server (Windows 2000 Server) and I
> > would like to ask a few questions:
> >
> > 1) Anything I should be aware of that will snag the transfer process?
> > 2) Is IIS 5.0 good enough to handle huge traffic loads when using
WiTango
> > 2000? (I have had miserable performance with IIS 4.0 and WiTango thus
the
> > Apache usage)
> > 3) do I HAVE to use IIS 5.0 if we were to develop .NET service tie-ins?
> > 4) Should I not worry about 2000 and stay on NT 4.0??
> >
> > Your opinions and advice will be appreciated.
> >
> > -Erik
> > --
> > +_____
> > |__ ___ ___ _____ _____ ____ _ _ | ___ __ ___+
> > | |___|| | | | |__| \ / | |___||__| |___
> > | | ||___ | |___| | \ | |____ | ||___| ___|
> > +
> > "A multi-disciplinary creative collective
> > based in Denver, Colorado"
> >
> > Erik Kulvinskas
> > www.factorylabs.com
> > ph: 303.573.9100
> > fx: 303.573.5975
> >
> >
________________________________________________________________________
> > TO UNSUBSCRIBE: send a plain text/US ASCII email to
[EMAIL PROTECTED]
> > with unsubscribe witango-talk in the message body
>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
