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.
Ensuring submitted hiscores are not fake
I have a small game that I would like to keep track og global hiscores for.
The basic is simple: username and score is submitted to a server for storage and later polling. However how do I ensure that these scores aren’t faked?
Ensuring submitted hiscores are not fake
I have a small game that I would like to keep track og global hiscores for.
The basic is simple: username and score is submitted to a server for storage and later polling. However how do I ensure that these scores aren’t faked?
Ensuring submitted hiscores are not fake
I have a small game that I would like to keep track og global hiscores for.
The basic is simple: username and score is submitted to a server for storage and later polling. However how do I ensure that these scores aren’t faked?
Desktop client server application, limiting text area field compromise with customers
We have a textarea field in a desktop client server application which in the end stores all the data in a database server, this text area is used to take notes and similar text areas have been put throughout our application as a marketing choice so that users can never blame the application for missing some fields and the marketing department can always answer “put it in the notes field”.
Desktop client server application, limiting text area field compromise with customers
We have a textarea field in a desktop client server application which in the end stores all the data in a database server, this text area is used to take notes and similar text areas have been put throughout our application as a marketing choice so that users can never blame the application for missing some fields and the marketing department can always answer “put it in the notes field”.
Desktop client server application, limiting text area field compromise with customers
We have a textarea field in a desktop client server application which in the end stores all the data in a database server, this text area is used to take notes and similar text areas have been put throughout our application as a marketing choice so that users can never blame the application for missing some fields and the marketing department can always answer “put it in the notes field”.
How to communicate side effects in a RESTful API on the server to the client?
I have been thinking a lot about Hypermedia REST-APIs for the last couple of weeks. One thing I am not quite sure about is how I want to model side effects on the server side.
How to communicate side effects in a RESTful API on the server to the client?
I have been thinking a lot about Hypermedia REST-APIs for the last couple of weeks. One thing I am not quite sure about is how I want to model side effects on the server side.
Implementing multiple tables for the same entity due to processing power on Client apps
I reached a design/architectural issue on the large application I’m working on, at the point of writing possibles solutions on a chalkboard. Our product consist of a client-server information system whose implementation was built on REST paradigms.