Eclipse Community Forums: Remote Application Platform (RAP)

Home » Eclipse Projects » Remote Application Platform (RAP) » RAP 1.2 plan

Thu, 18 September 2008 03:31

Eclipse User

Thanks for posting a RAP 1.2 plan !

It's good to see, where things are going ... I'm just missing a big point:

'memory and performance optimizations'
------------------------------------------------------------ -
- move to qooxdoo 0.8 (solves client side memory issues most apparent on
IE)
- change IdGenerator (server-side) to reuse id's of disposed widgets. This
fixes memory issues on IE in WidgetManager.js (client-side)
- reactive widget pooling (makes client side a lot faster)
- reduce memory cosumption on serverside (see bug #240143)
---------------------------

Are these points left out by intention or just not in there because the
plan is still in preliminary state ?

Re: RAP 1.2 plan [message #105524 is a reply to message #105504]

Thu, 18 September 2008 03:40

Eclipse User

Hi!

I`m sorry, but where i can found that post (about RAP 1.2 plan) ?

Thanks.

Re: RAP 1.2 plan [message #105532 is a reply to message #105524]

Thu, 18 September 2008 04:45

Eclipse User

On the main page (www.eclipse.org/rap) their is a link called 'plan' on
the left side, pointing to

http://www.eclipse.org/projects/project-plan.php?projectid=t echnology.rap

Re: RAP 1.2 plan [message #105585 is a reply to message #105504]

Thu, 18 September 2008 11:36

Eclipse User

Originally posted by: rherrmann.innoopract.com

thanks for the input. The points aren't left out by intention, just
the plan is still preliminary.

Apart from that, some of the issues you mentioned rather require
bugfixes that aren't listed in distinct plan items.

- Rüdiger

stefan.hansel@tolina.de wrote:
> Thanks for posting a RAP 1.2 plan !
>
> It's good to see, where things are going ... I'm just missing a big point:
>
> 'memory and performance optimizations'
> ------------------------------------------------------------ -
> - move to qooxdoo 0.8 (solves client side memory issues most apparent on
> IE)
> - change IdGenerator (server-side) to reuse id's of disposed widgets. This
> fixes memory issues on IE in WidgetManager.js (client-side)
> - reactive widget pooling (makes client side a lot faster)
> - reduce memory cosumption on serverside (see bug #240143)
> ---------------------------
>
> Are these points left out by intention or just not in there because the
> plan is still in preliminary state ?
>
>

Re: RAP 1.2 plan [message #105611 is a reply to message #105585]

Thu, 18 September 2008 12:57

Eclipse User

>>Apart from that, some of the issues you mentioned rather require
>> bugfixes that aren't listed in distinct plan items.

Yeah - was just brainstormed ...

Previous Topic:	RAP and MiGLayout
Next Topic:	Browser.execute() issue

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jun 07 12:10:30 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter