Eclipse Community Forums: Remote Application Platform (RAP) » Problems with event enqueueing and client-server synchronization

Home » Eclipse Projects » Remote Application Platform (RAP) » Problems with event enqueueing and client-server synchronization

Problems with event enqueueing and client-server synchronization [message #78744]

Wed, 19 March 2008 11:52

Eclipse User

Seems as problem (RWT 1.0.1): let's create Combo and add selection
listener does something might be time consuming (emulate it with
Thread.sleep()) and then dispaly modal dialog. When first time selection
made in Combo and while it is processing on server user still can change
selection again. It seems as new selection event is sent to server and
enqueued but when first selection event is processed and new selection
event picked from queue, new event is dropped since opened dialog "blocks
modality". As result selection in Combo changed in browser but no
selection event fired on server. The case is repeatable also from Controls
demo.

If some application logic heavily rely on selection change developers may
expect new bug in their bug tracker in case user does things fast or
server access is very slow:)

Re: Problems with event enqueueing and client-server synchronization [message #79062 is a reply to message #78744]

Mon, 24 March 2008 14:47

Eclipse User

Originally posted by: fappel.innoopract.com

Hi,

did you check whether the state of the combo was also changed on the
server, meaning that at least the client- and server-side state are
running in sync? But anyway this seems to be a non-trivial problem since
we don't want to block the UI for interactivity in case a background
request is running. I don't understand the bug-tracker context ...?

Ciao
Frank

-----Ursprüngliche Nachricht-----
Von: Denis Mukhin [mailto:durinda.dbry@gmail.com]
Bereitgestellt: Mittwoch, 19. März 2008 16:52
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Problems with event enqueueing and client-server
synchronization
Betreff: Problems with event enqueueing and client-server
synchronization

Seems as problem (RWT 1.0.1): let's create Combo and add selection
listener does something might be time consuming (emulate it with
Thread.sleep()) and then dispaly modal dialog. When first time selection
made in Combo and while it is processing on server user still can change
selection again. It seems as new selection event is sent to server and
enqueued but when first selection event is processed and new selection
event picked from queue, new event is dropped since opened dialog
"blocks modality". As result selection in Combo changed in browser but
no selection event fired on server. The case is repeatable also from
Controls demo.

If some application logic heavily rely on selection change developers
may expect new bug in their bug tracker in case user does things fast or
server access is very slow:)

Re: Problems with event enqueueing and client-server synchronization [message #79197 is a reply to message #79062]

Tue, 25 March 2008 12:59

Eclipse User

Originally posted by: rherrmann.innoopract.com

Hi,

I opened a bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=223852
feel free to comment on this bug if you can provide furhter information.

Cheers,
Rüdiger

Frank Appel wrote:
> Hi,
>
> did you check whether the state of the combo was also changed on the
> server, meaning that at least the client- and server-side state are
> running in sync? But anyway this seems to be a non-trivial problem since
> we don't want to block the UI for interactivity in case a background
> request is running. I don't understand the bug-tracker context ...?
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Denis Mukhin [mailto:durinda.dbry@gmail.com]
> Bereitgestellt: Mittwoch, 19. März 2008 16:52
> Bereitgestellt in: eclipse.technology.rap
> Unterhaltung: Problems with event enqueueing and client-server
> synchronization
> Betreff: Problems with event enqueueing and client-server
> synchronization
>
>
> Seems as problem (RWT 1.0.1): let's create Combo and add selection
> listener does something might be time consuming (emulate it with
> Thread.sleep()) and then dispaly modal dialog. When first time selection
> made in Combo and while it is processing on server user still can change
> selection again. It seems as new selection event is sent to server and
> enqueued but when first selection event is processed and new selection
> event picked from queue, new event is dropped since opened dialog
> "blocks modality". As result selection in Combo changed in browser but
> no selection event fired on server. The case is repeatable also from
> Controls demo.
>
> If some application logic heavily rely on selection change developers
> may expect new bug in their bug tracker in case user does things fast or
> server access is very slow:)
>

Previous Topic:	setText(String text) in MenuManager
Next Topic:	Table alignments - set different alignments on a single column

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jun 16 01:18:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter