Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 20768 invoked from network); 17 Nov 2001 20:41:01 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 17 Nov 2001 20:41:01 -0000 Received: (qmail 67 invoked by uid 97); 17 Nov 2001 20:40:55 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 13 invoked by uid 97); 17 Nov 2001 20:40:49 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 29976 invoked from network); 17 Nov 2001 20:40:47 -0000 Message-ID: <00b501c16f97$3bca40e0$31a1f40f@cv.hp.com> From: "Steve Loughran" To: "Ant Developers List" References: <054301c16f32$d19c1680$7600a8c0@CurtMicron> Subject: Re: better behavior when disconnected Date: Sat, 17 Nov 2001 10:39:44 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-ECS-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ah, you have noticed a failure of the 'deskto' versions of java -that they all make the assumption that a client is always on line, and there is no library call to check if the network is available. Yet studies have shown [Loughran, Secret Life of Notebooks, 2000] that network connectivity on a desktop replacement notebook varies wildly through the day. We really need an x-platform library to check for network status, maybe power levels too, but that would be a JCP project, not an apache one. Later on this weekend I will put into the CVS sandbox (I have to create that first) an early iteration of an extended set of http tasks; one key feature being that you can set a property when GET, HEAD or POST succeed. So you can have target probe for the web site being reachable (take the 30s hit) and use that property to control whether the rest of the get should take place. In the meantime, why not make the 'fetch remote files' a target which is not part of the default build path, huh? -steve ----- Original Message ----- From: "Curt Arnold" To: Sent: Friday, November 16, 2001 22:40 Subject: better behavior when disconnected I have a build script that uses extensive tasks to download static resource files from a web site (w3c.org) in preparation for building. Since I know the web site content should not change (since I'm using version specific URI's), as long as I have a local copy. I know its good. If I use usetimestamp="yes" then things move very quickly on successive builds, as long as there is a network connection and not in an airplane. In that case, the build becomes painful since every attempt to download files takes forever even though you already have the right files on your machine. If should be fairly trivial to add an attribute to that would indicate that the content is static and that if a local copy exists there is no need to attempt to connect to the source. "static" seems to be the most descriptive and unambiguious term that I could think of. Any thoughts? -- To unsubscribe, e-mail: For additional commands, e-mail: