Yes, if you set some user properties server side, it won't propagate to the this.core.user unless the user left/join the channel again. I already asked or something like this before. It's for me a major flaw in ape. But you can use some workaround (manual update the user info, create a server function who return the user properties in realtime, etc.) or you set the properties on connect or before the user join a channel.
Envoyé de mon iPhone Le 2012-09-17 à 10:52, apeman <[email protected]> a écrit : > Well its wierd, now I see in firebug i got response with public properties > ... and indeed on userJoin event i see it ... but when > i dump this.core.user i can see only public properties set in connect hook > > some code > > server side > > Ape.registerHookCmd("join", function(params, cmd) { > cmd.user.setProperty('foo', 'blast'); > }); > > > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
