keeping output to print on another page
Moderator: General Moderators
-
malcolmboston
- DevNet Resident
- Posts: 1826
- Joined: Tue Nov 18, 2003 1:09 pm
- Location: Middlesbrough, UK
keeping output to print on another page
ok, im basically looking at a nice way of passing results from page 1 to page 3 for eg.
page 1) Search form
page 2) go to a page saying "searching our database" (meta refresh to p3)
page 3) print "results";
i have thought of a few methods but they all have downsides
+ hold in a temp cookie (cookies can be disabled)
+ hold in a session var (no point in instantiating a session for this imo)
+ use GET parameter (unsafe)
+ use javascript auto post data from P2 (unsafe, can be circumvented)
any ideas?
page 1) Search form
page 2) go to a page saying "searching our database" (meta refresh to p3)
page 3) print "results";
i have thought of a few methods but they all have downsides
+ hold in a temp cookie (cookies can be disabled)
+ hold in a session var (no point in instantiating a session for this imo)
+ use GET parameter (unsafe)
+ use javascript auto post data from P2 (unsafe, can be circumvented)
any ideas?
-
malcolmboston
- DevNet Resident
- Posts: 1826
- Joined: Tue Nov 18, 2003 1:09 pm
- Location: Middlesbrough, UK
mark, i absolutely agree with you, i also hate this because in my opinion it just slows down the browsing experience, however this has been requested, thyey see it as a bit of a "noob" feature.
basically, its crap i know, but i need to know the best way of doing it, i could do it in many ways but theres too many pitfalls with each.
What im looking for, for eg. is something like hotscripts.com
basically, its crap i know, but i need to know the best way of doing it, i could do it in many ways but theres too many pitfalls with each.
What im looking for, for eg. is something like hotscripts.com
why not a form and hidden input types on page 2, the form can be post and know one would know without looking at the view source.
in fact if you wanted you probably could produce the query on page 1 put it onto page 2 in the form then when that page gets submitted it pass along the query to page 3. unsafe i know but just another thought.
in fact if you wanted you probably could produce the query on page 1 put it onto page 2 in the form then when that page gets submitted it pass along the query to page 3. unsafe i know but just another thought.
- artexercise
- Forum Commoner
- Posts: 33
- Joined: Thu Nov 20, 2003 9:38 am
- Location: Raleigh, NC
What about faking a page 2?
Put the "searching because I have to..." message in a div statment and give it a visibility style of "visible". If you declare this in the header and at the beginning of the body tag add an onLoad variable which points to a function that hides the "waiting..." statement and makes visible the valuable information kept neatly in another div.
That way you don't have to page stuff through a useless page, hide variables, etc...
JOE--
Put the "searching because I have to..." message in a div statment and give it a visibility style of "visible". If you declare this in the header and at the beginning of the body tag add an onLoad variable which points to a function that hides the "waiting..." statement and makes visible the valuable information kept neatly in another div.
That way you don't have to page stuff through a useless page, hide variables, etc...
JOE--
-
malcolmboston
- DevNet Resident
- Posts: 1826
- Joined: Tue Nov 18, 2003 1:09 pm
- Location: Middlesbrough, UK