javascript - Suggestions for writing a web client for an existing client/server application -


basically, existing application consists of c# server application running windows service , using sockets communicate along client applications connect server.

the server controls several camera systems: user can log in , move camera around, take video, , take photos.

the primary concern latency , user state memory without overhead.

basically model this:

camera <---> server <---> clients

i want:

camera <---> server <---> clients including web client

now, web side, guess 2 fundamental approaches are:

a) web client acts directly socket client connecting server directly. minimize latency. possible using html5/javascript without resorting flash?

b) web client communicates web server using web sockets or polling ajax. web server communicates application server. complications arise persisting server/server communication , handling user credentials , such. also, latency introduced. up-side client work behind firewalls/etc. long client can access web site.

basically, i've been doing lot of inconclusive research, @ point looking experienced input... recommend start? technologies smart investigate? allow rapid development/learning reasonable performance?

i recommend take different route:

camera <----> (existing, c#) server <----> (new webapp in) webserver <----> client

and translation stuff in server-sided app.

  • this has huge impact on security surface of application, camera server no longer exposed (untrusted) web clients, (trusted) web app.
  • it makes life easier: translation between simple , understood json on ajax request inside server-sided app trivial (and browser independant)

Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -