Client-server application where undo redu should be implemented? Server or client?

Question

0.00/5 (No votes)

See more:

.NET3.0

Hi I am developing large client server application. One client in different VMs and several servers on other VMs.
User creates entities in GUI
The GUI sends message via RabbitMQ to the server and the servers stores it in DB
The customer asked to implement undo redu operations between each save command.
Were the undo redu should be implemented? in the client? or server?
Thank you

What I have tried:

I am still in design level. Please suggest me correct way to design it.

Posted 18-Apr-21 20:33pm

Member 2434056

Updated 18-Apr-21 23:03pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Uroš Šmon · Answer 1 · 2021-04-18T23:03:00

It depends :)
If data is prepared as single enity, which is then sent to server and saved, you can have undo on client. You will need simple queue of commands.
If data is continously sent to server, you must implement undo on server, with added undo command. In this case you have to be careful with multiuser environment. This means you need extra table on server to store list of commands for every user. On client you call undo command on server and get back older version of data. What is old version and how you get it is different on how you store data. Simplest is saving new version and invalidate previous. Then you just send apropriate data back to client. More involved variant is to execute (on server) undo command on current version, save corrected version and send it back to client.
In every case you need to structure command and their undo and every change to data goes through command and parameters.
Hope this helps