Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Message-ID: <003b01c29c74$29757c60$6700000a@KYA>
From: "Chris Smith" <cdsmith@twu.net>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Subject: Re: [HttpClient] Using httpclient in applets (includes dirty fix)
Date: Thu, 5 Dec 2002 08:37:03 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

[Incidentally, someone let me know if you're getting two copies of my posts.
Invariably, I always send from my work account by accident, then remember to
change to personal address and resend.  Hope that's not causing problems.]

> This raises a funny question: is there a way for a library
> being called from an applet to test wether it's in an applet ?
> I would do it precisely with System.getProperties() catching
> the exception but there should be a cleaner way !

The problem you want to solve is not determining whether the code is running
in an applet, but whether you can get the system properties that you want.
The best way to solve that problem is very similar to what you said: try to
do so, and catch the SecurityException if it doesn't work.  This isn't just
about applets... it's about ANY code that's running under a security
manager, with a wide range of possible security policies.  That could
include applets, any of a bunch of other framework based environments, and
even some servlet containers.

The one change I'd suggest would be to make sure we always call getProperty
for the specific property we're interested in, rather than
System.getProperties... some security policies may allow access to some
properties, but not all.

--
www.designacourse.com
The Easiest Way to Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation