- The server should apply the property set immediately, not wait until

the event trundles through the queue, especially since the 'test' was
  being done immediately.
- Simplified some stuff on the server.
- Fixed up the test, as EZgame arrays will auto-grow.
- Do not set the property immediately on the client! Dangerz! We will add
  a new function for that, so that set() behaves like testAndSet() without the
  test, and set() behaves like setImmediate() without the immediate.
  (And there's no such thing as test and set immediately.)


git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@196 c613c5cb-e716-0410-b11b-feb51c14d237

src/as/com/threerings/ezgame/client/GameControlBackend.as

@@ -173,9 +173,6 @@ public class GameControlBackend
         _ezObj.ezGameService.setProperty(
             _ctx.getClient(), propName, encoded, index,
             false, null, createLoggingConfirmListener("setProperty"));
-
-        // set it immediately in the game object
-        _ezObj.applyPropertySet(propName, value, index);
     }
 
     public function testAndSetProperty_v1 (

src/as/com/threerings/ezgame/data/PropertySetEvent.as

@@ -34,6 +34,7 @@ public class PropertySetEvent extends NamedEvent
     // from abstract DEvent
     override public function applyToObject (target :DObject) :Boolean
     {
+        // since we're in actionscript, we're always on the client
         _oldValue =
             EZGameObject(target).applyPropertySet(_name, _data, _index);
         return true;