How to update dependency during runtime in my .NET application?
I have a server-client application. Sometimes the server is updated which requires some DLLs in the client to be updated as well (The DLLs are the dependencies of the main executable). For now, we have to close the client, manually deploy the DLLs, and then start the client again. This is kind of an inconvenience because the client is an automated application, so normally it doesn’t need any user intervention.
Suggestions for connecting .NET WPF GUI with Java SE Server
BACKGROUND
We are building a Java (SE) trading application which will be monitoring market data and sending trade messages based on the market data, and also on user defined configuration parameters.
Thin client Web browser?
Many times i have heard people saying that a particular hardware to be running a thin client web browser. But from the definition of “thin-client”, doesnt all browser qualify as a thin-client? as all they do is rendering the information sent from a remote server minimizing the work at the browser end?
Client-Server connection response timeout issues
User creates a folder in client and in the client-side code I hit an API to the server to make this persistent for that user. But in some cases, my server is so busy that the request timesout. The server has executed my request but timedout before sending a response back to client. The timeout set is 10 seconds in client. At this point the client thinks that server has not executed its request (of creating a folder) and ends up sending it again. Now I have 2 folders on the server but the user has created only 1 folder in the client. How to prevent this?
How to plan a client/server app networking architecture to cope with multiple unrelated exchanges of data?
I’m coding a server/client application pair in Java, as I learn about it. I have basic functionality of sending a message to the server and parsing it but in thinking about the big picture of their communication, I’m stumped about where to go from here.
Design question about a concurrent forking server
I’m in the early stages of designing a client/server application. The clients will be batch programs that read a file of customer contact data (name, address, email address, phone no’s) and pass these components to the server, which will add them (if not already present) to corresponding mySQL tables and return id’s for each component. In order to boost performance, the server will have spawned four “manager” servers, each tasked with looking up and possibly adding a new row, and will pass the four components via IPC to those managers so that they can work concurrently.
How to verify data from localStorage on a server
On my mobile app, I am storing the username of a logged in person, and downloading some data for the given/stored username. When the user checks for updates to his data content on the server, the server dishes out a delta of the content, based on the username. The app then updates its local display accordingly.
What are the advantages of a client/server architecture in webapplications as opposed to a server generated frontend application
In our company, we need to build a web interface onto an embedded Linux platform. I kind of see 2 options: You use a technology where the HTML and JavaScript is generated on the server side (Think JSP, Grails, but is is something that is using C++ and generates HTML/JavaScript) or you create a HTML5 ‘client’ application that talks to a JSON or XML generating backend.
Application protocols and state machines: designing a complicated server
I’m designing and prototyping a server that has the following characteristics:
Handle invalid text on server or fix on client in Client-Server application
I have developed a protocol for a Client-Server application and developed it in conjunction with another developer. The client application at this moment is written for the mobile phone.