Hello again, Are there any plans to incorporate a “native” inter-process event system in >> the future to facilitate application scenarios where controllers interact? >> > > Such as? >
My application has two major portions, a backend for communications with field devices and a user-facing web UI. Field devices periodically connect and, among other things, upload status information and data. Again among other things, the application evaluates the uploaded status information and may generate events used to communicate relevant aspects to the user via the web UI. Of course I can (and do) put that in a database and poll from that in web-UI-facing controllers, but an event-based system would be more efficient and avoid having to poll. Or to stick with a prototypical scenario, consider your WebSocket chat example, which will also not work with multiple processes. Especially with reactive, “real-time” applications, I'm sure there are plenty of scenarios where such interactions may come into play. Of course you may (and will likely) define this to be outside the scope of Mojolicious itself and recommend resorting to one of the aforementioned options in cases where this kind of interaction is required, but in my current situation, WebSockets would be so much more useful and easily usable if there was a built-in event system functional regardless of whether or not the context is multi-process. Marco -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
