Client/server model where the server rejects connections from *newer* clients
I’m using a piece of commercial software where the server will reject any attempt to connect to it from a newer client. In other words, you can use version 8 of the client to connect to a v10.0 server, but not version 10.1 of the client.
Client/server model where the server rejects connections from *newer* clients
I’m using a piece of commercial software where the server will reject any attempt to connect to it from a newer client. In other words, you can use version 8 of the client to connect to a v10.0 server, but not version 10.1 of the client.
Client/server model where the server rejects connections from *newer* clients
I’m using a piece of commercial software where the server will reject any attempt to connect to it from a newer client. In other words, you can use version 8 of the client to connect to a v10.0 server, but not version 10.1 of the client.
Make a monolithic architecture into something modular
Currently my architecture is a monolithic block that handles a really specific duty. Now it needs to be generalized.
Make a monolithic architecture into something modular
Currently my architecture is a monolithic block that handles a really specific duty. Now it needs to be generalized.
Make a monolithic architecture into something modular
Currently my architecture is a monolithic block that handles a really specific duty. Now it needs to be generalized.
Make a monolithic architecture into something modular
Currently my architecture is a monolithic block that handles a really specific duty. Now it needs to be generalized.
Refactoring sought for replacing shared data types in .NET component
I am in charge with updating a software product that is made up of two components the Controller process and the UI process. The Controller and the UI communicate via XML messages. Furthermore, the Controller is built on top of a shared library that implements a number of business flows.
Refactoring sought for replacing shared data types in .NET component
I am in charge with updating a software product that is made up of two components the Controller process and the UI process. The Controller and the UI communicate via XML messages. Furthermore, the Controller is built on top of a shared library that implements a number of business flows.
A specific problem with architecturing a part of our application
Firstly, I’ll try to describe the real world model of what we are trying to express in C# code.