Closed valignatev closed 9 years ago
Because of ugly CORS errors I tried to follow Issue #73 with no results. Then I checked that tutorial show me that CORS error too but work well in same time.
For what I can see in your code your are missing a way to trigger the router so you can send the information you want when a user login or logout. Using a SelfPublishModel will trigger the call to the router but only on CRUD operations to that model, in this case the model affected is Session.
I see you do user.is_invited = true != user.is_invited; but the only field you can update is username, add that field in the model and serializer if you want to trigger an update with your actual approach.
Hope it helps. Bye.
Using a SelfPublishModel will trigger the call to the router but only on CRUD operations to that model
Thank you. Now it makes sense. I thought it will triggered on any Model.objects.all() change. Never go deep into source. So I have to add another field and change it. See if it works
Yes it works! Thanks you one more time!
I wrote simple application which shows currently loggen in users, it works well and I want make it realtime. So I have my model and custom manager:
Serializer:
Router:
And controller:
So when I log out some user in second browser window nothing happend. Through debugger I realized that onChannelMessage does not called.
Hovever tutorial worked well for me.