• 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: Backtracking - That Age Old Problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Backtracking - That Age Old Problem


  • Subject: Re: Backtracking - That Age Old Problem
  • From: Jonathan Rochkind <email@hidden>
  • Date: Thu, 07 Aug 2003 13:53:26 -0500

I'm getting confused thinking about this stuff, I have a bunch of ideas and I'm not sure which are best, or which would work. But it strikes me that am important fact is if you've got a session or not. You say that you are using direct actions---that doesn't neccesarily commit us to avoiding a session, or to using one. In your application, is it important to avoid creating a session? Or is it okay to have a session, so long as all pages are bookmarkable? Or what? What are your requirements here, that lead you to use direct actions in the first place?

Whether or not we have a session available determines the success of some of the options I'm thinking of. Without using a session.... I'm having trouble thinking of anything particularly good. Although it depends on the maximum and typical count of the result set, too.

--Jonathan

At 11:35 AM 8/7/2003 -0700, Sam Barnum wrote:
You've got a few options here. I think your current setup isn't necessarily a bad one, it doesn't use much memory for storing the objects, at any rate. As long as the queries aren't huge, then just refetching the record isn't the much of a strain.

Some other options I can think of:
* Javascript (ugh) if you're sure the user came from a list page, history.go(-1) will take them back. This puts the least load on the server, and is also the most error-prone.
* Instead of passing the search parameters, you could save the actual NSArray of objects being displayed to your session (or in the component somehow)
* Keep things the same. If you're displaying raw rows in your list, at least you know your data will reflect any changes made since the list was displayed.


Thoughts, comments, constructive criticism???


On Thursday, August 7, 2003, at 09:42 AM, Jonathan Fleming wrote:

Hi Everyone,

I've never been able to sort this problem out on the side of DirectActions. To go back to a results page (an array of listed items in a repitition) I pass the search values through to my section page or view page where I hide the text box values, but provide a form and return button that will basically search the same query again therefore giving me back the exact same results that I came from in my results page - which is what I want.
Obviously this is sending untold requests to the server therefore puting a strain on it which ain't good at all. Does anyone know how to properly go back to a results page when you are using direct actions?


Examples would be welcomed. Thank you.

Kind regards
Jonathan

_________________________________________________________________
Express yourself with cool emoticons - download MSN Messenger today! http://www.msn.co.uk/messenger
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Backtracking - That Age Old Problem (From: "Jonathan Fleming" <email@hidden>)

  • Prev by Date: Re: Backtracking - That Age Old Problem
  • Next by Date: Re: Backtracking - That Age Old Problem
  • Previous by thread: Re: Backtracking - That Age Old Problem
  • Next by thread: Re: Backtracking - That Age Old Problem
  • Index(es):
    • Date
    • Thread