-Original Message-
From: Charles Wiltgen [mailto:lists;wiltgen.net]
Sent: 13 November 2002 18:28
Here's what I
was using:
Form:
form method=post action=http://domain.com/; name=the_form
input type=hidden name=foo value=DUMMY
/form
Link:
a
Additionally...
-Original Message-
From: Charles Wiltgen [mailto:lists;wiltgen.net]
Sent: 13 November 2002 18:28
Ford, Mike [LSS] wrote...
...But why would they even see that in the first place
If I want them
to click on a button to do something, I simply
Ford, Mike [LSS] wrote...
a href=http://coremessaging.com/;
onClick=document.the_form.foo.value='5';
document.the_form.submit();Next/a
... but there's *still* no GET variables involved here...
I'm weighing the pros and cons of two different methods:
-Original Message-
From: Charles Wiltgen [mailto:lists;wiltgen.net]
Sent: 12 November 2002 20:14
For example, take my spinner object example. By using
Invisible Get,
after clicking on the increment spinner button the user sees
http://www.getsome.com/
rather than
Ford, Mike [LSS] wrote...
...But why would they even see that in the first place If I want them
to click on a button to do something, I simply make it part of a FORM METHOD=
POST and the value gets fed to my script via $_POST without the user seeing
it in the URL. Why
Seems to me like this would generate a lot of extra server traffic, and a
little confusion... The only benefit I can see is that you're getting rid of
ugly page URLs.
Problems I can see:
1. sessions need to be carried around... if your user has cookies turned
off, or you wish not to use them;
a)
Justin,
Many thanks for the reply. I didn't provide enough detail in some spots,
and I'll attempt to clarify.
Seems to me like this would generate a lot of extra server traffic, and a
little confusion... The only benefit I can see is that you're getting rid of
ugly page URLs.
User
On 11/12/02 10:15 AM, Charles Wiltgen ([EMAIL PROTECTED]) wrote:
So, your URLs will actually look like
http://www.site.com/article.php?PHPSESSID=12413523245546453
No problem, since the user will never see this and other session properties
using this Invisible Get method even with cookies
Pablo wrote...
Your method assumes something about your users: that they click on links.
This may be unlikely, but what if a user uses the 'copy URL to clipboard'
(or equivalent) feature of their browser? It could be pasted into an e-mail,
posted to a newsgroup, etc.
Exactly -- this is the
-Original Message-
From: Charles Wiltgen [mailto:lists;wiltgen.net]
Sent: 12 November 2002 18:48
Your method assumes something about your users: that they
click on links.
This may be unlikely, but what if a user uses the 'copy URL
to clipboard'
(or equivalent) feature of
Ford, Mike [LSS] wrote...
I've been staying out of this discussion as I've been sure there was something
I was missing, but this comment I really don't understand -- if you use PHP's
built-in sessions, all that gets into the URL (maybe, if cookies are disabled)
is the session ID
Well, you seem so sure it will work, so give it a go... I can't see how, but
am totally willing to learn!
Have you got any info on invisible gets?
Justin French
Creative Director
http://Indent.com.au
Web Developent
Graphic Design
--
PHP General
Justin French wrote...
Well, you seem so sure it will work, so give it a go... I can't see how, but
am totally willing to learn!
Have you got any info on invisible gets?
It's simple, which is one thing I like about it. My submit.php looks like
this:
?php
session_start();
On Tue, 12 Nov 2002 15:55:52 -0800, you wrote:
It's simple, which is one thing I like about it. My submit.php looks like
this:
?php
session_start();
header('Location: ' . $_REQUEST['target']);
[snip]
I'm curious...your redirect doesn't include the session ID, so how you
maintain
Michael Sims wrote...
It's always been my experience that trans sid doesn't append the SID to header
redirects. You have to do it manually (I use the SID constant for this
purpose).
When I test on a browser with cookies disabled, I imagine I'll find that I
have to do that. That's okay,
On Tue, 12 Nov 2002 18:28:53 -0800, you wrote:
[snip]
My Invisible GET method avoids all of this.
If you get an example of this up and running somewhere why don't you
post a link...
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Monday 11 November 2002 23:56, Charles Wiltgen wrote:
B.C. Lance wrote...
one reason that i could think of for not including session id into URL
and using cookies would be copy paste.
users could just copy and paste the url and send it to his/her friends.
and it could be a
I posted this yesterday:
Specifically, I'm considering using hidden fields for persistent object
properties because (1) I don't want cookies to be an issue, (2) I prefer not
to have session IDs appear in a URL, and (3) I prefer not to use require a
database just to store persistent
Hello,
I'm about to implement session management, and I'm considering rolling my
own instead of using PHP's.
Specifically, I'm considering using hidden fields for persistent object
properties because (1) I don't want cookies to be an issue, (2) I prefer not
to have session IDs appear in a URL,
on 11/11/02 7:41 AM, Charles Wiltgen ([EMAIL PROTECTED]) wrote:
Are there drawbacks to storing persistent object properties as a serialized
value in hidden fields that I'm missing? This is a newbie's first major web
application, so I really appreciate your input.
Doesn't that mean you'd
At 22:41 10.11.2002, Charles Wiltgen said:
[snip]
I'm about to implement session management, and I'm considering rolling my
own instead of using PHP's.
Hmm - NIH syndrome?
(not invented here)
Specifically, I'm considering using hidden fields for persistent
Justin wrote...
...every link across your site has to be a form submit. Yuk!!!
Yeah, yuk. I'm very silly and didn't realize this until after I'd posted.
It's possible since links will be generated automatically, but yuk.
Ernest wrote...
Hmm - NIH syndrome?
(not invented here)
No, I'm far
22 matches
Mail list logo
