HashMap -> HashObjectMap
Hashtable -> HashMap The one regularly used is now called HashMap. It can have keys of simple flash datatypes, as well as objects that implement Hashable. HashObjectMap has the ability to use nearly any object as a key, but pays a price for it and should be avoided unless you need it. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@4591 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
@@ -2,7 +2,7 @@ package com.threerings.presents.client {
|
||||
|
||||
import flash.utils.getTimer; // function import
|
||||
|
||||
import com.threerings.util.Hashtable;
|
||||
import com.threerings.util.HashMap;
|
||||
import com.threerings.util.Wrapped;
|
||||
|
||||
import com.threerings.presents.data.InvocationMarshaller_ListenerMarshaller;
|
||||
@@ -367,10 +367,10 @@ public class InvocationDirector
|
||||
|
||||
/** Used to keep track of invocation service listeners which will
|
||||
* receive responses from invocation service requests. */
|
||||
protected var _listeners :Hashtable = new Hashtable();
|
||||
protected var _listeners :HashMap = new HashMap();
|
||||
|
||||
/** Used to keep track of invocation notification receivers. */
|
||||
protected var _receivers :Hashtable = new Hashtable();
|
||||
protected var _receivers :HashMap = new HashMap();
|
||||
|
||||
/** All registered receivers are maintained in a list so that we can
|
||||
* assign receiver ids to them when we go online. */
|
||||
|
||||
Reference in New Issue
Block a user