Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-10 Thread Daniel Rall
Jim Redman <[EMAIL PROTECTED]> writes: > Daniel, > > On 2002.06.10 16:14 Daniel Rall wrote: > >> protected String getProperty(String name, String defaultValue) >> { >> try >> { >> return System.getProperty(name); >> } >> catch (SecurityException

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-10 Thread Jim Redman
Daniel, On 2002.06.10 16:14 Daniel Rall wrote: > protected String getProperty(String name, String defaultValue) > { > try > { > return System.getProperty(name); > } > catch (SecurityException useDefault) > { > return default

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-10 Thread Daniel Rall
"John Wilson" <[EMAIL PROTECTED]> writes: > - Original Message - > From: "Jim Redman" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, June 08, 2002 2:39 PM > Subject: Re: Dictionary vs. Hashtable in XmlRpc.java > >

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-08 Thread Jim Redman
On 2002.06.08 07:50 John Wilson wrote: > > > System.getProperty > > > > also always throws and prints in IE so that causes more problems in > > applets. > > Jim, > > Would explicitly catching the exception help? I'm working from memory, but my recollection is that it prints an exception

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-08 Thread John Wilson
- Original Message - From: "Jim Redman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, June 08, 2002 2:39 PM Subject: Re: Dictionary vs. Hashtable in XmlRpc.java > System.getProperty > > also always throws and prints in IE so that causes m

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-08 Thread Jim Redman
, June 07, 2002 1:54 AM > Subject: Re: Dictionary vs. Hashtable in XmlRpc.java > > > [snip] > > > Yeah, we can drop it if anyone wants to submit a patch. I'm still a > > bit unsure about how this will affect use from applets, but as a 1.2 > > plug-in is a

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-08 Thread John Wilson
- Original Message - From: "Daniel Rall" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 07, 2002 1:54 AM Subject: Re: Dictionary vs. Hashtable in XmlRpc.java [snip] > Yeah, we can drop it if anyone wants to submit a patch. I'm still a &g

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-07 Thread Jim Redman
The jar is also 250K. After we've hit our application with the Ant "GenJar" task, that's about the size of the typical application - so it would double the download time. The license didn't seem to specifically limit pulling out certain classes but I wouldn't want to be the final judge of wh

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Tim Peierls
Tim Peierls wrote: > > There is a 1.1 collections compatibility jar from Sun. Would > > that do the trick for your 1.1 user base? Jim Redman wrote: > I can't find the jar to download, nor the license, but in priciple I > have no objections. ... And I'm definitly not opposed to performance > impro

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Jim Redman
Tim, On 2002.06.06 20:38 Tim Peierls wrote: > > There is a 1.1 collections compatibility jar from Sun. Would > that do the trick for your 1.1 user base? > I can't find the jar to download, nor the license, but in priciple I have no objections. I didn't know the jar existed - we may have use

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Tim Peierls
Jim Redman wrote: > I'd be opposed to any changes that require Java2. I'm also not sure > why the change is proposed. Is there some pressing reason to drop the > Hashtable? Hashtable and Vector are concrete classes, not interfaces. As of JDK 1.2 they are synchronized implementations of the Map a

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Jim Redman
We still have a bunch of customers using raw IE and Netscape 4.x. So I'd be opposed to any changes that require Java2. I'm also not sure why the change is proposed. Is there some pressing reason to drop the Hashtable? Jim On 2002.06.06 18:54 Daniel Rall wrote: > Tim Peierls <[EMAIL PROTECTE

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Daniel Rall
Tim Peierls <[EMAIL PROTECTED]> writes: >> On Thu, 2002-06-06 at 13:59, Gus Mueller wrote: >> > I was wondering if anyone saw any problems with using a >> > Dictionary instead of a Hastable in XmlRpc.java >> > josh lucas wrote: > > >> afaik, we are still trying to stay compatible with 1.1 and

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Tim Peierls
> On Thu, 2002-06-06 at 13:59, Gus Mueller wrote: > > I was wondering if anyone saw any problems with using a > > Dictionary instead of a Hastable in XmlRpc.java > josh lucas wrote: > > afaik, we are still trying to stay compatible with 1.1 and thus > can't use Dictionary... Dictionary is si

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Gus Mueller
josh lucas ([EMAIL PROTECTED]) wrote: > afaik, we are still trying to stay compatible with 1.1 and thus can't > use Dictionary... I'm pretty sure Dictionary is part of 1.1- http://java.sun.com/products/jdk/1.1/docs/api/java.util.Dictionary.html -gus -- "Christmas means carnage!" -- Ferdinand,

Re: Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread josh lucas
On Thu, 2002-06-06 at 13:59, Gus Mueller wrote: > I was wondering if anyone saw any problems with using a Dictionary instead > of a Hastable in XmlRpc.java for the function writeObject(Object obj) > > My problem is, that when using a Hashtable, the order of the objects put > in are not kept the

Dictionary vs. Hashtable in XmlRpc.java

2002-06-06 Thread Gus Mueller
I was wondering if anyone saw any problems with using a Dictionary instead of a Hastable in XmlRpc.java for the function writeObject(Object obj) My problem is, that when using a Hashtable, the order of the objects put in are not kept the same (it uses a hash!) so I had created a class that imp