Hi Lenya devs,
everytime the meta data tab is requested, a continuation is created.
Even if you modify and save the meta data, another continuation is
created, because the screen is displayed again. This behaviour
unnecessarily increases memory consumption.
I see two options to avoid the problem:
1. Don't create continuations
2. Separate "modify meta-data" usecase
The major problem with approach 1. is that it doesn't detect read-write
conflicts - with concurrent modification, the second commit overrides
the changes of the first one. This is especially problematic with our
current approach: All meta data values are saved, not only the modified
ones.
Approach 2. requires additional clicks, but I think we could live with that.
How about this approach: The meta data screen has no submit button by
default, but next to each (editable) field is an "Edit" button. When you
click it, an optimistic usecase is started, which only manipulates this
single field. The "Edit" button changes to "Save". The changes are sent
to the server using an asynchronous request. If you're familiar with
Flickr - I imagine it to work like editing photo titles.
WDYT?
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
