Eclipse Community Forums: Remote Application Platform (RAP)

Home » Eclipse Projects » Remote Application Platform (RAP) » How do blocking popups work?

How do blocking popups work? [message #98993]

Sun, 20 July 2008 00:21

Eclipse User

Hi all,

I notice that Window.open() in RAP is blocking. I am intrigued. Given
the remote natue of the UI and the request/response paradigm (with
associated lifecycle) can anyone offer an explanation of how this works?
... or dare I ask, is it documented anywhere?

I have been code trawling but, to be honest, it seems a little opaque.

Appreciated.

Greg.

Re: How do blocking popups work? [message #99097 is a reply to message #98993]

Mon, 21 July 2008 08:41

Eclipse User

Originally posted by: rsternberg.innoopract.com

Hi Greg,

Greg wrote:
> I notice that Window.open() in RAP is blocking. I am intrigued. Given
> the remote natue of the UI and the request/response paradigm (with
> associated lifecycle) can anyone offer an explanation of how this
> works? .. or dare I ask, is it documented anywhere?
>
> I have been code trawling but, to be honest, it seems a little opaque.

since the implementation of Display#readAndDispatch in 1.1M2 [1],
blocking dialogs work pretty much the same as in RCP. When in blocked
state, Window#open() runs the event loop itself and returns control back
to the caller when the window is being closed.

How readAndDispatch works goes down to the very core of RAP. From the
bird's-eye view, every session has its own UI thread which runs the
event loop and sleeps between requests.

Regards, Ralf

[1] http://www.eclipse.org/rap/noteworthy/news_11M2.php

Re: How do blocking popups work? [message #99168 is a reply to message #99097]

Mon, 21 July 2008 22:13

Eclipse User

Hi Ralf,

yes, at a high level I can see that going on. Some further looking into
the code revealed the additional thread usage for each session and that
started to make thing a bit clearer. I can see it does go to the very
heart of it. I haven't quite got my head around how the lifecycle code
works and how this sudden thread sleeping during lifecycle processing
affects it all, but slowly slowly ...

Thanks for the reply.

Greg.

Re: How do blocking popups work? [message #99183 is a reply to message #99168]

Tue, 22 July 2008 04:23

Eclipse User

Hi,

the inner workings of readAndDispatch and the apartment threading of RWT
a a little complex as it needs to be multi-user aware. But we will
provide a design document soon which explains the lifecycle and the
readAndDispatch implementation in much more detail.

Greets
Benny

Greg wrote:
> Hi Ralf,
>
> yes, at a high level I can see that going on. Some further looking into
> the code revealed the additional thread usage for each session and that
> started to make thing a bit clearer. I can see it does go to the very
> heart of it. I haven't quite got my head around how the lifecycle code
> works and how this sudden thread sleeping during lifecycle processing
> affects it all, but slowly slowly ...
>
> Thanks for the reply.
>
> Greg.
>

Re: How do blocking popups work? [message #99987 is a reply to message #99183]

Thu, 24 July 2008 19:08

Eclipse User

Thanks Benny,

Magic. I am sure that will be welcomed by the community.

Yes, it is complex isn't it. Attempting to guess what multiple threads
are doing and how they interact just by looking at the code can be, well,
less than illuminating!

I've not managed to be able to get a debug session going at all, so
sticking with the code will do for now.

I can mostly understand how the dispatch loop does it thing, and I reckon
I'm almost there with how the threadswitch works, but not quite with what
the callback manager's role is in all this.

Anyways, thanks for the response. Appreciated.

Greg.

Previous Topic:	Problem deploying .war file for tomcat
Next Topic:	Startup level of fragments

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jun 08 13:09:27 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter