On 3/23/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] schrieb: > > On 3/22/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > >> [EMAIL PROTECTED] schrieb: > >>> On 3/21/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > >> >> everytime the meta data tab is requested, a continuation is created. > >> >> 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(). > My question was rather related to the onChange() listeners: I'd expect a > POST request to be sent for each typed character. But I guess this could > be solved using timers etc. > > Thanks for elaborating! > -- Andreas
onChange() triggers when the field is exited, not as each character is typed. No timers are needed. Read the code behind the demo with "View Source". http://solprovider.net/fieldupdates.html The onBlur and onUnload events help MSIE work better. Mozilla does not need the extra code since onChange is sensible. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
