RE: URI-1.22

-Original Message- From: Gisle Aas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 03, 2002 10:48 PM To: Keary Suska Cc: Libwww Perl Subject: Re: URI-1.22 Keary Suska <[EMAIL PROTECTED]> writes: > I don't wish to complicate issues any, but it seems to me more sensible to > specify

Re: URI-1.22

Keary Suska <[EMAIL PROTECTED]> writes: > I don't wish to complicate issues any, but it seems to me more sensible to > specify the desired separator string as an optional parameter to the URI > constructor. I think this is a clever hack. If instead of constructing objects of the URI class you c

Re: URI-1.22

Keary Suska <[EMAIL PROTECTED]> writes: > I don't wish to complicate issues any, but it seems to me more sensible to > specify the desired separator string as an optional parameter to the URI > constructor. This also avoids the mentioned caveats, as it would otherwise > have to be explicitly chan

Re: URI-1.22

I don't wish to complicate issues any, but it seems to me more sensible to specify the desired separator string as an optional parameter to the URI constructor. This also avoids the mentioned caveats, as it would otherwise have to be explicitly changed. I recall there was a question of instance va

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > On Wed, 2002-09-04 at 01:05, Gisle Aas wrote: > > > > However, if the query_param method interface has been there for only a > > > couple of days now, perhaps it wouldn't be impossible to change it to > > > have the sepchar there and quickly release URI

Re: URI-1.22

On Wed, 2002-09-04 at 01:05, Gisle Aas wrote: > > However, if the query_param method interface has been there for only a > > couple of days now, perhaps it wouldn't be impossible to change it to > > have the sepchar there and quickly release URI-1.23. > > The sepchar proposal as it stands now is

Re: URI-1.22

On Wed, 2002-09-04 at 01:07, Sean M. Burke wrote: > Personally, I think the W3C's whole ;-for-& idea is something that should > have been done from the beginning, but which it's maybe too late to do now > -- since one never knows if a given server/CGI will be able to make sense > of ;-as-separ

Re: URI-1.22

At 08:43 2002-09-03 -0700, Gisle Aas wrote: >Some have suggested that $u->query_form should just split on both >[&;]. I have two problems with that; 1) I'm not totally convinced >that URIs like ?foo=1;2;3&bar=1 does not exist and 2) how do we know >what to use for joining parameters. Personally,

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > > $u->query_param(foo => 1); > > print $u; # prints "?foo=1" > > print $u->query-sepchar; # prints "&" > > > > $u->query_param(foo => 1..3); > > print $u; # prints "?foo=1;foo=2;foo=3" > > Shouldn't

Re: URI-1.22

On Tue, 2002-09-03 at 22:56, Gisle Aas wrote: > > > Some have suggested that $u->query_form should just split on both > > > [&;]. I have two problems with that; 1) I'm not totally convinced > > > that URIs like ?foo=1;2;3&bar=1 does not exist and > > > > Hmm. I wonder if anything that accepts

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > > Some have suggested that $u->query_form should just split on both > > [&;]. I have two problems with that; 1) I'm not totally convinced > > that URIs like ?foo=1;2;3&bar=1 does not exist and > > Hmm. I wonder if anything that accepts both of delimit

Re: URI-1.22

On Tue, 2002-09-03 at 18:43, Gisle Aas wrote: > > How about an option to someway tell query_param to use (if not default > > to) ";" as the separator in query strings instead of "&"? > > I actually thought a bit about that when I did URI::QueryParam, but I > did not manage to come up with an API

Re: URI-1.22

On Tue, 2002-09-03 at 10:36, Sean M. Burke wrote: > >- > > I wonder -- is that ;-for-& thing specified in some RFC too? Well, the only one I'm aware of is RFC 1866 (HTML 2.0), section 8.2.1. Don't know if that counts as a useful refere

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > How about an option to someway tell query_param to use (if not default > to) ";" as the separator in query strings instead of "&"? I actually thought a bit about that when I did URI::QueryParam, but I did not manage to come up with an API that I liked.

Re: how to grab the cookie set by javascript?

You have to emulate the javascript code and set the same cookie. $user_agent->cookie_jar->set_cookie( $version, $key, $val, $path, $domain, $port, $path_spec, $secure, $maxage, $discard, \%rest);

how to grab the cookie set by javascript?

the cookie is set during a form submission. an onclick() function get to invoked and a CookieSet function is being called,cookie get created then. how do i grab the cookie in this case? here is the javascript code and form code.