Note that there are some explanatory texts on larger screens.

plurals
  1. POSuggestions for writing a web client for an existing client/server application
    text
    copied!<p>Basically, the existing application consists of a C# server application running as a windows service and using sockets to communicate along with client applications that connect to this server.</p> <p>The server essentially controls several camera systems: user can log in and move camera around, take video, and take photos.</p> <p>The primary concern is latency and user state memory without too much overhead.</p> <p>Basically the model is like this:</p> <p>Camera &lt;---> Server &lt;---> Clients</p> <p>I want:</p> <p>Camera &lt;---> Server &lt;---> Clients including web client</p> <p>Now, for the web side, I guess the two fundamental approaches are:</p> <p>a) Web client acts directly as a socket client connecting to the server directly. This would minimize latency. Is this possible using HTML5/JavaScript without resorting to something like flash?</p> <p>b) Web client communicates to web server using something like web sockets or polling with AJAX. Web server communicates with application server. Now complications arise with persisting the server/server communication and handling user credentials and such. Also, some latency is introduced. The up-side is the client will work behind firewalls/etc. as long as the client can access the web site.</p> <p>Basically, I've been doing a lot of inconclusive research, so at this point I am looking for experienced input... Where would you recommend I start? What technologies would I be smart to investigate? What will allow for the most rapid development/learning with reasonable performance?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload