Is having a bi directional message queue a design smell?
I have an architecture with 1 backend server and multiple frontend servers.
Need to add websocket support to a single page that’s running a wsgi service
Current setup. I have a legacy ERP system (Thoroughbred) and i then have several in house applications (CRM, WMS) and a website that interact with it via an xml server and straight ODBC connections. The CRM, WMS, and website are all python applications running the Turbogears framework (not married to this its just the first framework i used and has served me well).
Need to add websocket support to a single page that’s running a wsgi service
Current setup. I have a legacy ERP system (Thoroughbred) and i then have several in house applications (CRM, WMS) and a website that interact with it via an xml server and straight ODBC connections. The CRM, WMS, and website are all python applications running the Turbogears framework (not married to this its just the first framework i used and has served me well).
Mixing REST and websocket in the same API
A bit of background first, I’m working on an application that manages a piece of physical equipment with motors, stuff like that. When I started on the project, there was an existing application, built with Labview and that was in a poor state. The part of the code that manages the hardware, the “drivers” were in a better shape. The goal was to write a new app, in .Net, but reusing as much as possible the existing drivers.
Mixing REST and websocket in the same API
A bit of background first, I’m working on an application that manages a piece of physical equipment with motors, stuff like that. When I started on the project, there was an existing application, built with Labview and that was in a poor state. The part of the code that manages the hardware, the “drivers” were in a better shape. The goal was to write a new app, in .Net, but reusing as much as possible the existing drivers.
Mixing REST and websocket in the same API
A bit of background first, I’m working on an application that manages a piece of physical equipment with motors, stuff like that. When I started on the project, there was an existing application, built with Labview and that was in a poor state. The part of the code that manages the hardware, the “drivers” were in a better shape. The goal was to write a new app, in .Net, but reusing as much as possible the existing drivers.
Mixing REST and websocket in the same API
A bit of background first, I’m working on an application that manages a piece of physical equipment with motors, stuff like that. When I started on the project, there was an existing application, built with Labview and that was in a poor state. The part of the code that manages the hardware, the “drivers” were in a better shape. The goal was to write a new app, in .Net, but reusing as much as possible the existing drivers.
Mixing REST and websocket in the same API
A bit of background first, I’m working on an application that manages a piece of physical equipment with motors, stuff like that. When I started on the project, there was an existing application, built with Labview and that was in a poor state. The part of the code that manages the hardware, the “drivers” were in a better shape. The goal was to write a new app, in .Net, but reusing as much as possible the existing drivers.
Mixing REST and websocket in the same API
A bit of background first, I’m working on an application that manages a piece of physical equipment with motors, stuff like that. When I started on the project, there was an existing application, built with Labview and that was in a poor state. The part of the code that manages the hardware, the “drivers” were in a better shape. The goal was to write a new app, in .Net, but reusing as much as possible the existing drivers.
Are web sockets a browser feature or supplied by a specific OS version?
Are web sockets a web browser feature, developed and evolving as the browser developers want, or this feature dependent on the OS version?