If you really are worried about using standard session 
stuff you could always store the variables on the server 
in a table or text file and just pass a query string of

http://blah.com/page.php?sid=123456

And use the sid to target the information after the redirect.

Cheers,
Justin.

> -----Original Message-----
> From: Nikolai Devereaux [mailto:yomama@u...]
> Sent: 19 November 2002 23:25
> To: professional php
> Subject: [pro_php] RE: Posting Variables On Redirect
> 
> 
> 
> Hey Mark,
> 
> 
> > I had a feeling I might be confusing the two. The trouble 
> is, I don't
> > *really* want to use session data, but the only alternative 
> really is to
> > write an awfully long query string, so it looks like 
> session data will
> > have to be the solution.
> 
> 
> When it comes down to it, you're persisting data on the 
> server.  That's a
> session var, however you slice it.
> 
> If you'd like to persist that data in the URL rather than in 
> $_SESSION, so be
> it, but be aware that URLs are limited in length.  If you try 
> to append a whole
> bunch of variables to the query string, the link might not 
> work.  I've come
> across this problem in phpMyAdmin, when I click the link to 
> edit a query or
> whatever.  The query is too long and the link doesn't work.
> 
> Using $_SESSION is, imho, the easiest approach.  Is there a 
> specific reason why
> you'd prefer to avoid it?
> 
> If you're worried about using cookies, you can use custom 
> session handlers, and
> just pass the session ID on the URL.  The data to be 
> persisted is stored in
> files or a database, and the session ID doesn't have to be 
> generated by PHP...
> it can be the unique id of your sessions table in the 
> database, the unsigned,
> autoincrement integer primary key field.
> 
> 
> Take care,
> 
> nik
> 
> 
>