Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: markspace <-@.> Newsgroups: comp.lang.java.programmer Subject: Re: tools for programming applets Date: Sun, 22 May 2011 20:26:44 -0700 Organization: A noiseless patient Spider Lines: 21 Message-ID: References: <028d2009-98b7-43a3-b02d-83eaa89db79e@glegroupsg2000goo.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 23 May 2011 03:26:54 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="8FmyTa30jaHydmbsw/NXBQ"; logging-data="25034"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19jgp8eebFq1X8zMrnxDFBZSTaWplMCuc8=" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 In-Reply-To: Cancel-Lock: sha1:WFvRMuCA+crywaF9moy1ZL9smUw= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4438 On 5/22/2011 7:06 PM, Lew wrote: > Really, not a very good idea to put tests on the production server. > Actually, a really terrible, terrible idea. Ghastly. I wasn't thinking of doing the entire test suite, all through development, on a production system. I was thinking of only doing just a kind of final system test. After the product is deemed stable, you install it on production server, with out removing the old system. Then you can quickly switch back to the old system if the new system fails for some reason. The real issue with testing both production and development on the same box would be resources. CPU time, memory: those are things that production tends not to be able to spare. So this would have to be carefully planned out. But running the old system and the new, at the same time, in parallel, sounds like it might allow one to do an "instant" deployment, at least in some circumstances.