Re: Maintain server state of a page + Javascript page navigation
Re: Maintain server state of a page + Javascript page navigation
- Subject: Re: Maintain server state of a page + Javascript page navigation
- From: David Avendasora <email@hidden>
- Date: Mon, 6 Jul 2009 08:54:11 -0400
On Jul 6, 2009, at 7:54 AM, shravan kumar wrote:
Hi Group,
Could you please advise me a solution to achieve below functionality:
Scenario:
-------------
I have a page which gets all the data like text content [3000 lines
or more], images info [about 500 or more] once when the user
requests for this page.
Once this data from the server has arrived, we will be displaying
this whole data part by part by splitting this data into sub-pages
through javascript. So, user actually sees the sub-page rather the
whole page received from the server.
There can be around 40 sub-pages or more.
While navigating through each of these sub-pages user may perform a
server action like edit some text and save, rotate an image and
save, ... and all these actions do not refresh the whole page/ sub-
page (like we see in ajax implementations) and just update a
particular field.
I assume that there might be some time-gap say 10 minutes or more
between each of the server actions performed by the user.
During these times as you know, we have to maintain the session of
this user in the server (this can be achieved through lets say
session timeout value), state of this page in the server, ...
Problem:
-------------
How can I maintain the state of this page (generally whenever we do
a submit WO app returns with a new context info, correct?), so all
my actions are valid and there are issues of Broken pipe/ page not
in the cache/ ...
Unless I'm missing something, you can just extend the length of the
Session timeout to be what you anticipate the longest a user will need
to respond. 10 minutes I believe is the default, but you can make it
anything. Editing Contexts (your user's pools of objects) are
maintained as part of the user's Session and you control which editing
context is used, or if a new one is created for each action.
Maintaining state is one of WO's core functions, you just have to
determine exactly what state and for how long you want to maintain it
for your particular situation
I thought of just pinging the server every few seconds for some
dummy data like: how are you doing? or something like gmail does?
However, I do not know how to exactly implement this behavior.
You should not need to do this at all. WO will maintain state as long
as the session hasn't timed out or you don't start using a different
editing context.
With all this said, it sounds like you are trying to implement a rich
client in a web UI. Have you considered Java Client at all for this
functionality? It would make managing the client-server interaction
much easier since you will actually have EOs on the client that you
can manipulate using normal Java instead of having to write Javascript
to do it.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden