Thanks. You are right, keeping input and output separate is good thing.
Marking as resolved.
Hi
Thanks for responding so quickly.
I don’t think it actually would increase the server load that much. The first check would be that is the visitor allowed to change the table. I believe that all the required information for that is already retrieved to memory.
However, I don’t know if it’s from the UI design point of view a desired solution. Maybe it ought to be a option for embedding the table if editing / adding is allowed.
Architecturally this would probably mean lot of work so I do understand that you not interested in this. The classes seem to be divided where they are used, not in OO fashion.
I like the plan on reducing clicks on the backed 🙂
BR,
Tommi
