solprovider apache.org schrieb:
> On 3/21/08, Andreas Hartmann <andreasapache.org> wrote:
>> 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
[...]
> My vote would be for #1 because I have psychoses about
locking systems
> and limited-duration server-based data storage.
If we submit only a single value (e.g. using AJAX or by
comparing old
and new values), #1 might be OK. Mabye we could send the
original value
together with the new value so that the server can check for
concurrent
changes and output a warning (avoid read-write conflicts)
without
server-side locking.
> If using #2, do not add clicks. AJAX needs neither the
submit button
> nor "edit" links. Just use onChange() and
similar events to trigger
> the sendInformation().
Won't that generate a lot of traffic? Or is it easy to add a
timer which
submits only if no change happened e.g. for 1 second?
Personally, I
don't mind to add at least a "Save" button.
Hitting the return key
should also work.
> Even a monitor thread checking every 5 seconds
> to test for changed fields is better than adding
clicks. (I also have
> a psychosis about creating listener threads for trigger
events.)
I don't quite understand the bit about the listener threads
- would you
mind elaborating? Thanks a lot!
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org
|
