this commit adds a callback that a controller can register that can be triggered from the application (backend). This callback can then render data to the client. In this way you can get rid of the periodic timer function, that in my opinion doesnt belong to most event based systems. Please tell me what you think about this and sorry for no feature branch.
for a demo see my edited version of akitaonrails websocket chat example.
Problem is, it doesn't scale across multiple processes/hosts. Usually it's better to use something like Redis pub/sub. But using periodic timers does the job with traditional dbs like MySQL.
this commit adds a callback that a controller can register that can be triggered from the application (backend). This callback can then render data to the client. In this way you can get rid of the periodic timer function, that in my opinion doesnt belong to most event based systems. Please tell me what you think about this and sorry for no feature branch.
for a demo see my edited version of akitaonrails websocket chat example.