• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Maintain server state of a page + Javascript page navigation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Maintain server state of a page + Javascript page navigation


  • Subject: Re: Maintain server state of a page + Javascript page navigation
  • From: shravan kumar <email@hidden>
  • Date: Tue, 7 Jul 2009 23:01:10 -0700 (PDT)

Thanks for your response Mike.

What is Giandiua btw? Google says it is a Chocolate from Italy!!!

The page am referring is just one of the pages of a wizard, which has sub-pages. The whole wizard runs through component actions.

I was actually about following situation:

When we have long response component displayed upon initiating a request, and we see long response until we have a response. Once after the response let's say I just hide long response component and show the main component, now user cannot perform any actions in this main component and we might receive errors like: You have exceeded 30 pages limit/ page out of cache... this is because the context bound to the action element is older. Am I correct (Mike) ?

I understand by your saying switching to direct actions, we can get away from this issue if we use direct actions. But am wondering if I can use component actions and direct actions freely. I hope I can validate whether the direct action request is initiated by a logged-in valid user, so my direct actions are not floating freely.

---------------

If I use component actions, can you advise me how can I have all the elements, app in the latest context?

Thank You,
Shravan Kumar. M
--------------------------------------


Monday, July 6, 2009 7:14 PM
From:
"Mike Schrag" <email@hidden>
To:
"WO Dev Group" <email@hidden>
seems to me like you're swimming against the tide here ... i think you need to rethink this architecture.  you're basically sending the users the entire site, which makes this more of a Sproutcore/Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo.
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/ ...

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 around
http://mail.yahoo.com
 _______________________________________________
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

  • Follow-Ups:
    • Re: Maintain server state of a page + Javascript page navigation
      • From: Mike Schrag <email@hidden>
  • Prev by Date: Re: Maintain server state of a page + Javascript page navigation
  • Next by Date: Re: And the beat goes on...
  • Previous by thread: Re: Maintain server state of a page + Javascript page navigation
  • Next by thread: Re: Maintain server state of a page + Javascript page navigation
  • Index(es):
    • Date
    • Thread