onJoinRoomError event fired on non-existing room join reques
Posted: 19 Sep 2010, 17:05
Hello,
In the SmartFoxClient.as in the joinRoom function, why not to add:
right after the trace:
I have seen some posts where developers complain about the missing error. And this one seems to give the best answers:
http://forums.smartfoxserver.com/viewto ... nroomerror
But still, I do not get why only the trace to the ide?
This is no hack-attack prevention right?
And I see Lapo's point
any user can make a "private game", a room which should not be shown in the interface's room list. Then the user can say to his friend "buddy, I am waiting you in the room /MyGameName/". His friend can hit a "joinPrivateRoom" button and enter the "MyGameName" string and try to join the hidden room. Everything is alright until you try to join non exsisting room.
I couldn't find any other useful and easy solution than modifying the SmartFoxClient.as itself with this extra line.
I would patch it for myself on every new SmartFoxClient.as update if I have to. And if my case is so rare.
But isn't it better this error event to be fired?
I really cannot understand what is the benefit of not firing it?
~
In the SmartFoxClient.as in the joinRoom function, why not to add:
Code: Select all
this.onJoinRoomError('Requested room to join does not exist!')
Code: Select all
trace("SmartFoxError: requested room to join does not exist!")
http://forums.smartfoxserver.com/viewto ... nroomerror
But still, I do not get why only the trace to the ide?
This is no hack-attack prevention right?
And I see Lapo's point
But right now I have the following case:The RoomList should be the only source from which the client can decide where to go.
any user can make a "private game", a room which should not be shown in the interface's room list. Then the user can say to his friend "buddy, I am waiting you in the room /MyGameName/". His friend can hit a "joinPrivateRoom" button and enter the "MyGameName" string and try to join the hidden room. Everything is alright until you try to join non exsisting room.
I couldn't find any other useful and easy solution than modifying the SmartFoxClient.as itself with this extra line.
I would patch it for myself on every new SmartFoxClient.as update if I have to. And if my case is so rare.
But isn't it better this error event to be fired?
I really cannot understand what is the benefit of not firing it?
~