Is it advisable to switch AJAX routes (called with $.Ajax in jquery) like:
- GET /animals
- GET /animals/[id]
- POST /animals
To socket.io events (event bound on client and server for client response):
- emit("animals:read")
- emit("animals:read", {id:asdasd})
- emit("animals:write", animalData)
Or should I solely use socket.io for data push to the client?
[EDIT] I see a potential issue if I don't utilize socket.io for my POST route. The problem lies in not being able to easily broadcast data using the client's socket:
Server:
on("animals:write", function(data){
saveAnimal(req.data)
socket.broadcast(...)
emit("animals:write", writtenAnimal)
})
VS
app.post(function(req,res){
saveAnimal(data)
// unable to broadcast :(
res.send(201,writtenAnimal)
})
I will definitely push data to clients in other requests, ensuring all clients have at least 1 socket connection.