| Client Runtime Data... [message #80420] |
Mon, 31 March 2008 16:42  |
Eclipse User |
|
|
|
Originally posted by: michael.suwiryo.siemens.com
Hi all,
I'm new to RAP. I'm trying to understand further about the client runtime
contextual data used in RAP application.
My question is where this client runtime contextual data is held across
multiple requests. Is this runtime data always stored as part of the user
session or somewhere else on the server?
Let's say I have a table widget with two columns with 100 data (row) on each
column. I retrieved the data by either making a call to database or making a
SOA call. After the widget is rendered on the browser, where is this all UI
data (table data) stored?
Moreover, if I sort the table on the browser, the event is triggered, the
server updates the server side widget status, process the events and send
the response back (deltas) to the browser. There are two widget data that
are communicating in this example. One is in the client side widget which is
handled by qooxdoo, and another is server side widget data. Is this server
side widget data stored as part of the user session? if not, where is it
stored?
If it's true that the data is stored as part of the user session, the user
session may get very big and this will lead to slower performance. In other
words, the memory footprint on the server will increase as more users are
using the RAP application.
Thanks.
Regards,
Michael Suwiryo
|
|
|
| Re: Client Runtime Data... [message #80691 is a reply to message #80420] |
Tue, 01 April 2008 09:15  |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
RAP provides a thin client approach that uses rich widgets for user
interface composition. This means data model state is stored completely
on the server. This is common to all server-centric webapplications of
the last years and the concepts of how to deal with this are well known
- data caches as one example which are available even for clustered
environments. But it is true that RAP isn't developed to replace
content-management systems with millions of users a day.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Michael Suwiryo [mailto:michael.suwiryo@siemens.com]
Bereitgestellt: Montag, 31. März 2008 22:43
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Client Runtime Data...
Betreff: Client Runtime Data...
Hi all,
I'm new to RAP. I'm trying to understand further about the client
runtime contextual data used in RAP application.
My question is where this client runtime contextual data is held across
multiple requests. Is this runtime data always stored as part of the
user session or somewhere else on the server?
Let's say I have a table widget with two columns with 100 data (row) on
each column. I retrieved the data by either making a call to database or
making a SOA call. After the widget is rendered on the browser, where is
this all UI data (table data) stored?
Moreover, if I sort the table on the browser, the event is triggered,
the server updates the server side widget status, process the events and
send the response back (deltas) to the browser. There are two widget
data that are communicating in this example. One is in the client side
widget which is handled by qooxdoo, and another is server side widget
data. Is this server side widget data stored as part of the user
session? if not, where is it stored?
If it's true that the data is stored as part of the user session, the
user session may get very big and this will lead to slower performance.
In other words, the memory footprint on the server will increase as more
users are using the RAP application.
Thanks.
Regards,
Michael Suwiryo
|
|
|
Powered by
FUDForum. Page generated in 0.02596 seconds
Home