mugle-dev team mailing list archive
-
mugle-dev team
-
Mailing list archive
-
Message #00371
Re: Behaviour of remove
Well the other option is when you remove a devteam for example, the
client side removes the key from the clientside object, which we then
have to pass back and check all the keys the client side gives,
whereas now we don't accept any of the keys from the clientside, so
association and dissociation has to be called manually for any extra
associations you want to set up
On 25/05/2011, at 12:00 PM, Matt Giuca <matt.giuca@xxxxxxxxx> wrote:
I believe the association and disassociation is set up correctyl (I
checked about half the classes last night). Note you DO specifically
have to call these add and remove methods on the client side in the
UI for security reasons.
So you can disassociate a user from a devteam or a game from a
devteam? Maybe we can put that in the UI (but not for this milestone).
I don't quite follow though .. how can client side UI have anything
to do with security?
Follow ups
References