epilogue
epilogue copied to clipboard
socket.io integration
I am playing about getting my client models and collections to be reactive and have realised that they need to listen to a subject from sockets.io identical to the url e.g. a model is at /Model Name/id and a collection at /parent model/parent id/model so just send messages on those subjects and thus simplify the backbone model to be able to use the same thing (minus any query parameters). the message transmission is done via a sequelize hook, but it's seeming logical that the application of that hook to the respective model should move to the REST generator, where it can decide what the url===message subject should be.
@mark-lester do you have a question here?
Should socket.io support be integrated into the REST generator.