To Remote or not to remote, and if so: how ? that is the question.
-
Hi Everyone, I have a question about remoting. We have a server app running on a TCP port where clients can connect to do do all sorts of stuff. These clients are connected over the internet. At the backend, we have our database which the clients query and some other applications ( including management app for the clients, a website etc) connects to this database. Recently, we started moving everything into remoting hosted on IIS for easier use and scalibility ( since most of these apps are doing the same stuff in the same database) Now my question is regarded to the Server application. In there, we have a list of clients ( list(of MyClientClass) to represent the collection of connected clients. I would like to be able to query this "live" list of connected clients and do stuff with them from my different applications. Moreover, i would like to be able to put multiple of these Servers but still be able to treat the connected clients as one collection (if possible). I was thinking remoting both the "client class" as the list of connected clients. Although this has a few minor performance drawbacks ( servers and IIS hosted remoting are in the same place connected over 1 Gbit Ethernet so that should not be such a worry right ?), it makes it easy to interact with the connected client collection. Is this the way to go or should i consider other options ? Thanks !
Do Or Don't, there is no "try catch ex as exception end try"