You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Remus Stratulat <rs...@interakt.ro> on 2002/07/09 10:56:45 UTC
cookies
Will be a version with support for multiple cookies and cookie handling?
Right now in SOAPHTTPConnection the responseHeaders can hold only the
last cookie that was set (due to the fact that it's a Hashtable). I know
that the SOAP's main goal is not session maintaining but I'm confronting
with this problem. Along with this, an interface for accessing the
cookieHeader and cookieHeader2 is necessary as some of us need to work
with the cookies. Right now I will deal with this on my own as I can but
out there might be others that don't have the time or will to modify
your source code.
Best regards,
Remus Stratulat
--
/**
* Remus Stratulat - KrysalIDE maintainer
* InterAkt Online.
*
* @phone +40 90 07 24 07
* @email rstratulat@interakt.ro
* @web http://www.interakt.ro
*/
Able to send object to .NET service but the member values are
still set to null.
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Able to send object to .NET service but the member values are still set to null.
To elaborate, the .NET service is receiving the object as a parameter to one of
its method but the values of the individual members are not copied. They are
still set to null.
Can anyone help?
Thanks,
Indrasish.
Able to send object to .NET service but the member values are
still set to null.
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Able to send object to .NET service but the member values are still set to null.
To elaborate, the .NET service is receiving the object as a parameter to one of
its method but the values of the individual members are not copied. They are
still set to null.
Can anyone help?
Thanks,
Indrasish.
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
I misread the Netscape spec. The semicolons are separating attributes from
one another (just like the RFCs), not cookies from one another. Further, a
quick look at some servers I have available shows that Expires is commonly
used. So much for IETF standards! I will add proper handling of this comma
to the CVS code shortly.
Thanks.
Scott Nichol
----- Original Message -----
From: "Scott Nichol" <sn...@scottnichol.com>
To: <so...@xml.apache.org>
Sent: Thursday, July 11, 2002 3:02 PM
Subject: Re: cookies
> Regarding "There is a comma in Max-Age/expires field", while I see that
> there is a comma in the Netscape Expires value (Expires did not make it to
> RFC level), I do not see how there could be a comma in Max-Age.
> Specifically, both RFC 2109 says "The Max-Age attribute defines the
lifetime
> of the cookie, in seconds. The delta-seconds value is a decimal
> non-negative integer" and RFC 2965 says "The value of the Max-Age
attribute
> is delta-seconds,
> the lifetime of the cookie in seconds, a decimal non-negative integer."
>
> I also notice that the Netscape spec uses a semi-colon to separate
> name=value pairs within the cookie, which is how it can handle the comma
> embedded in the value for Expires. It is not obvious how to determine
that
> a Set-Cookie header follows the Netscape spec rather than RFC 2109. The
> code can try to apply 2109, and if there appear to be invalid attributes,
> try parsing it by the Netscape spec. I am curious, do you know of any
> servers that use the Netscape Set-Cookie syntax other than old versions of
> Netscape?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Remus Stratulat" <rs...@interakt.ro>
> To: <so...@xml.apache.org>
> Cc: "Scott Nichol" <sn...@scottnichol.com>
> Sent: Wednesday, July 10, 2002 7:34 AM
> Subject: Re: cookies
>
>
> > I have a proposal for Cookie.jar
> > I do not know what is the proper format or way to propose a change for a
> > file so I attached here the code that I modified from Cookie.jar along
> > with comments that explains the changes.
> >
> > Remus Stratulat
> >
> > --
> > /**
> > * Remus Stratulat - KrysalIDE maintainer
> > * InterAkt Online.
> > *
> > * @phone +40 90 07 24 07
> > * @email rstratulat@interakt.ro
> > * @web http://www.interakt.ro
> > */
> >
> >
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
I misread the Netscape spec. The semicolons are separating attributes from
one another (just like the RFCs), not cookies from one another. Further, a
quick look at some servers I have available shows that Expires is commonly
used. So much for IETF standards! I will add proper handling of this comma
to the CVS code shortly.
Thanks.
Scott Nichol
----- Original Message -----
From: "Scott Nichol" <sn...@scottnichol.com>
To: <so...@xml.apache.org>
Sent: Thursday, July 11, 2002 3:02 PM
Subject: Re: cookies
> Regarding "There is a comma in Max-Age/expires field", while I see that
> there is a comma in the Netscape Expires value (Expires did not make it to
> RFC level), I do not see how there could be a comma in Max-Age.
> Specifically, both RFC 2109 says "The Max-Age attribute defines the
lifetime
> of the cookie, in seconds. The delta-seconds value is a decimal
> non-negative integer" and RFC 2965 says "The value of the Max-Age
attribute
> is delta-seconds,
> the lifetime of the cookie in seconds, a decimal non-negative integer."
>
> I also notice that the Netscape spec uses a semi-colon to separate
> name=value pairs within the cookie, which is how it can handle the comma
> embedded in the value for Expires. It is not obvious how to determine
that
> a Set-Cookie header follows the Netscape spec rather than RFC 2109. The
> code can try to apply 2109, and if there appear to be invalid attributes,
> try parsing it by the Netscape spec. I am curious, do you know of any
> servers that use the Netscape Set-Cookie syntax other than old versions of
> Netscape?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Remus Stratulat" <rs...@interakt.ro>
> To: <so...@xml.apache.org>
> Cc: "Scott Nichol" <sn...@scottnichol.com>
> Sent: Wednesday, July 10, 2002 7:34 AM
> Subject: Re: cookies
>
>
> > I have a proposal for Cookie.jar
> > I do not know what is the proper format or way to propose a change for a
> > file so I attached here the code that I modified from Cookie.jar along
> > with comments that explains the changes.
> >
> > Remus Stratulat
> >
> > --
> > /**
> > * Remus Stratulat - KrysalIDE maintainer
> > * InterAkt Online.
> > *
> > * @phone +40 90 07 24 07
> > * @email rstratulat@interakt.ro
> > * @web http://www.interakt.ro
> > */
> >
> >
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
Regarding "There is a comma in Max-Age/expires field", while I see that
there is a comma in the Netscape Expires value (Expires did not make it to
RFC level), I do not see how there could be a comma in Max-Age.
Specifically, both RFC 2109 says "The Max-Age attribute defines the lifetime
of the cookie, in seconds. The delta-seconds value is a decimal
non-negative integer" and RFC 2965 says "The value of the Max-Age attribute
is delta-seconds,
the lifetime of the cookie in seconds, a decimal non-negative integer."
I also notice that the Netscape spec uses a semi-colon to separate
name=value pairs within the cookie, which is how it can handle the comma
embedded in the value for Expires. It is not obvious how to determine that
a Set-Cookie header follows the Netscape spec rather than RFC 2109. The
code can try to apply 2109, and if there appear to be invalid attributes,
try parsing it by the Netscape spec. I am curious, do you know of any
servers that use the Netscape Set-Cookie syntax other than old versions of
Netscape?
Scott Nichol
----- Original Message -----
From: "Remus Stratulat" <rs...@interakt.ro>
To: <so...@xml.apache.org>
Cc: "Scott Nichol" <sn...@scottnichol.com>
Sent: Wednesday, July 10, 2002 7:34 AM
Subject: Re: cookies
> I have a proposal for Cookie.jar
> I do not know what is the proper format or way to propose a change for a
> file so I attached here the code that I modified from Cookie.jar along
> with comments that explains the changes.
>
> Remus Stratulat
>
> --
> /**
> * Remus Stratulat - KrysalIDE maintainer
> * InterAkt Online.
> *
> * @phone +40 90 07 24 07
> * @email rstratulat@interakt.ro
> * @web http://www.interakt.ro
> */
>
>
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
Regarding "There is a comma in Max-Age/expires field", while I see that
there is a comma in the Netscape Expires value (Expires did not make it to
RFC level), I do not see how there could be a comma in Max-Age.
Specifically, both RFC 2109 says "The Max-Age attribute defines the lifetime
of the cookie, in seconds. The delta-seconds value is a decimal
non-negative integer" and RFC 2965 says "The value of the Max-Age attribute
is delta-seconds,
the lifetime of the cookie in seconds, a decimal non-negative integer."
I also notice that the Netscape spec uses a semi-colon to separate
name=value pairs within the cookie, which is how it can handle the comma
embedded in the value for Expires. It is not obvious how to determine that
a Set-Cookie header follows the Netscape spec rather than RFC 2109. The
code can try to apply 2109, and if there appear to be invalid attributes,
try parsing it by the Netscape spec. I am curious, do you know of any
servers that use the Netscape Set-Cookie syntax other than old versions of
Netscape?
Scott Nichol
----- Original Message -----
From: "Remus Stratulat" <rs...@interakt.ro>
To: <so...@xml.apache.org>
Cc: "Scott Nichol" <sn...@scottnichol.com>
Sent: Wednesday, July 10, 2002 7:34 AM
Subject: Re: cookies
> I have a proposal for Cookie.jar
> I do not know what is the proper format or way to propose a change for a
> file so I attached here the code that I modified from Cookie.jar along
> with comments that explains the changes.
>
> Remus Stratulat
>
> --
> /**
> * Remus Stratulat - KrysalIDE maintainer
> * InterAkt Online.
> *
> * @phone +40 90 07 24 07
> * @email rstratulat@interakt.ro
> * @web http://www.interakt.ro
> */
>
>
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: cookies
Posted by Remus Stratulat <rs...@interakt.ro>.
I have a proposal for Cookie.jar
I do not know what is the proper format or way to propose a change for a
file so I attached here the code that I modified from Cookie.jar along
with comments that explains the changes.
Remus Stratulat
--
/**
* Remus Stratulat - KrysalIDE maintainer
* InterAkt Online.
*
* @phone +40 90 07 24 07
* @email rstratulat@interakt.ro
* @web http://www.interakt.ro
*/
Re: cookies
Posted by Remus Stratulat <rs...@interakt.ro>.
On Tue, 2002-07-09 at 18:59, Scott Nichol wrote:
> > Ok, I got it. Thank you. But still no access to them. Some getters and
> > setters for cookies and cookies2 would be nice.
>
> Good idea. I'll throw that in today.
>
> > And by the way, why don't you make some of the fields and methods
> > protected so one can easily extend from your classes. Now I have to
> > rewrite the entire class or modify the sources directly.
>
> It's hard to be perfect in anticipating where everyone will want to extend
> the class hierarchies.
You are right.
> I think the code usually tries to err on the side of
> added "safety", so private is much more common than protected. There would
> probably be more use of protected if Java had borrowed the C++ meaning of
> the modifier, rather than opening protected up to the whole package.
>
> So, the approach generally taken is to change the modifier from private to
> protected during a refactoring that makes it necessary. If it would benefit
> you to have some particular method(s) changed so you can subclass, post it
> to the list. Better yet, post your extension to the list as a patch so that
> we can all benefit from your work.
At this point no one would benefit from my work as I've done an work
around in SOPAHTTPConnection and HTTPUtils so I can get access to all
the cookies. With the latest updates from you this changes are of no
use.
Thanks again for your feedback and understanding.
Remus Stratulat
>
> Scott Nichol
>
> >
> > Best regards,
> > Remus Stratulat
> >
> >
> > On Tue, 2002-07-09 at 16:10, Scott Nichol wrote:
> > > What you say is true of the latest release, but the current source,
> > > available through the nightly distribution or CVS tree, supports
> multiple
> > > cookies.
> > >
> > > Scott Nichol
> > >
> > > ----- Original Message -----
> > > From: "Remus Stratulat" <rs...@interakt.ro>
> > > To: <so...@xml.apache.org>
> > > Sent: Tuesday, July 09, 2002 4:56 AM
> > > Subject: cookies
> > >
> > >
> > > > Will be a version with support for multiple cookies and cookie
> handling?
> > > >
> > > > Right now in SOAPHTTPConnection the responseHeaders can hold only the
> > > > last cookie that was set (due to the fact that it's a Hashtable). I
> know
> > > > that the SOAP's main goal is not session maintaining but I'm
> confronting
> > > > with this problem. Along with this, an interface for accessing the
> > > > cookieHeader and cookieHeader2 is necessary as some of us need to work
> > > > with the cookies. Right now I will deal with this on my own as I can
> but
> > > > out there might be others that don't have the time or will to modify
> > > > your source code.
> > > >
> > > > Best regards,
> > > > Remus Stratulat
> > > >
> > > >
> > > > --
> > > > /**
> > > > * Remus Stratulat - KrysalIDE maintainer
> > > > * InterAkt Online.
> > > > *
> > > > * @phone +40 90 07 24 07
> > > > * @email rstratulat@interakt.ro
> > > > * @web http://www.interakt.ro
> > > > */
> > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > > For additional commands, e-mail: <ma...@xml.apache.org>
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > --
> > /**
> > * Remus Stratulat - KrysalIDE maintainer
> > * InterAkt Online.
> > *
> > * @phone +40 90 07 24 07
> > * @email rstratulat@interakt.ro
> > * @web http://www.interakt.ro
> > */
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
/**
* Remus Stratulat - KrysalIDE maintainer
* InterAkt Online.
*
* @phone +40 90 07 24 07
* @email rstratulat@interakt.ro
* @web http://www.interakt.ro
*/
Re: cookies
Posted by Remus Stratulat <rs...@interakt.ro>.
I have a proposal for Cookie.jar
I do not know what is the proper format or way to propose a change for a
file so I attached here the code that I modified from Cookie.jar along
with comments that explains the changes.
Remus Stratulat
--
/**
* Remus Stratulat - KrysalIDE maintainer
* InterAkt Online.
*
* @phone +40 90 07 24 07
* @email rstratulat@interakt.ro
* @web http://www.interakt.ro
*/
Re: cookies
Posted by Remus Stratulat <rs...@interakt.ro>.
On Tue, 2002-07-09 at 18:59, Scott Nichol wrote:
> > Ok, I got it. Thank you. But still no access to them. Some getters and
> > setters for cookies and cookies2 would be nice.
>
> Good idea. I'll throw that in today.
>
> > And by the way, why don't you make some of the fields and methods
> > protected so one can easily extend from your classes. Now I have to
> > rewrite the entire class or modify the sources directly.
>
> It's hard to be perfect in anticipating where everyone will want to extend
> the class hierarchies.
You are right.
> I think the code usually tries to err on the side of
> added "safety", so private is much more common than protected. There would
> probably be more use of protected if Java had borrowed the C++ meaning of
> the modifier, rather than opening protected up to the whole package.
>
> So, the approach generally taken is to change the modifier from private to
> protected during a refactoring that makes it necessary. If it would benefit
> you to have some particular method(s) changed so you can subclass, post it
> to the list. Better yet, post your extension to the list as a patch so that
> we can all benefit from your work.
At this point no one would benefit from my work as I've done an work
around in SOPAHTTPConnection and HTTPUtils so I can get access to all
the cookies. With the latest updates from you this changes are of no
use.
Thanks again for your feedback and understanding.
Remus Stratulat
>
> Scott Nichol
>
> >
> > Best regards,
> > Remus Stratulat
> >
> >
> > On Tue, 2002-07-09 at 16:10, Scott Nichol wrote:
> > > What you say is true of the latest release, but the current source,
> > > available through the nightly distribution or CVS tree, supports
> multiple
> > > cookies.
> > >
> > > Scott Nichol
> > >
> > > ----- Original Message -----
> > > From: "Remus Stratulat" <rs...@interakt.ro>
> > > To: <so...@xml.apache.org>
> > > Sent: Tuesday, July 09, 2002 4:56 AM
> > > Subject: cookies
> > >
> > >
> > > > Will be a version with support for multiple cookies and cookie
> handling?
> > > >
> > > > Right now in SOAPHTTPConnection the responseHeaders can hold only the
> > > > last cookie that was set (due to the fact that it's a Hashtable). I
> know
> > > > that the SOAP's main goal is not session maintaining but I'm
> confronting
> > > > with this problem. Along with this, an interface for accessing the
> > > > cookieHeader and cookieHeader2 is necessary as some of us need to work
> > > > with the cookies. Right now I will deal with this on my own as I can
> but
> > > > out there might be others that don't have the time or will to modify
> > > > your source code.
> > > >
> > > > Best regards,
> > > > Remus Stratulat
> > > >
> > > >
> > > > --
> > > > /**
> > > > * Remus Stratulat - KrysalIDE maintainer
> > > > * InterAkt Online.
> > > > *
> > > > * @phone +40 90 07 24 07
> > > > * @email rstratulat@interakt.ro
> > > > * @web http://www.interakt.ro
> > > > */
> > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > > For additional commands, e-mail: <ma...@xml.apache.org>
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > --
> > /**
> > * Remus Stratulat - KrysalIDE maintainer
> > * InterAkt Online.
> > *
> > * @phone +40 90 07 24 07
> > * @email rstratulat@interakt.ro
> > * @web http://www.interakt.ro
> > */
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
/**
* Remus Stratulat - KrysalIDE maintainer
* InterAkt Online.
*
* @phone +40 90 07 24 07
* @email rstratulat@interakt.ro
* @web http://www.interakt.ro
*/
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
> Ok, I got it. Thank you. But still no access to them. Some getters and
> setters for cookies and cookies2 would be nice.
Good idea. I'll throw that in today.
> And by the way, why don't you make some of the fields and methods
> protected so one can easily extend from your classes. Now I have to
> rewrite the entire class or modify the sources directly.
It's hard to be perfect in anticipating where everyone will want to extend
the class hierarchies. I think the code usually tries to err on the side of
added "safety", so private is much more common than protected. There would
probably be more use of protected if Java had borrowed the C++ meaning of
the modifier, rather than opening protected up to the whole package.
So, the approach generally taken is to change the modifier from private to
protected during a refactoring that makes it necessary. If it would benefit
you to have some particular method(s) changed so you can subclass, post it
to the list. Better yet, post your extension to the list as a patch so that
we can all benefit from your work.
Scott Nichol
>
> Best regards,
> Remus Stratulat
>
>
> On Tue, 2002-07-09 at 16:10, Scott Nichol wrote:
> > What you say is true of the latest release, but the current source,
> > available through the nightly distribution or CVS tree, supports
multiple
> > cookies.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Remus Stratulat" <rs...@interakt.ro>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, July 09, 2002 4:56 AM
> > Subject: cookies
> >
> >
> > > Will be a version with support for multiple cookies and cookie
handling?
> > >
> > > Right now in SOAPHTTPConnection the responseHeaders can hold only the
> > > last cookie that was set (due to the fact that it's a Hashtable). I
know
> > > that the SOAP's main goal is not session maintaining but I'm
confronting
> > > with this problem. Along with this, an interface for accessing the
> > > cookieHeader and cookieHeader2 is necessary as some of us need to work
> > > with the cookies. Right now I will deal with this on my own as I can
but
> > > out there might be others that don't have the time or will to modify
> > > your source code.
> > >
> > > Best regards,
> > > Remus Stratulat
> > >
> > >
> > > --
> > > /**
> > > * Remus Stratulat - KrysalIDE maintainer
> > > * InterAkt Online.
> > > *
> > > * @phone +40 90 07 24 07
> > > * @email rstratulat@interakt.ro
> > > * @web http://www.interakt.ro
> > > */
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> --
> /**
> * Remus Stratulat - KrysalIDE maintainer
> * InterAkt Online.
> *
> * @phone +40 90 07 24 07
> * @email rstratulat@interakt.ro
> * @web http://www.interakt.ro
> */
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
> Ok, I got it. Thank you. But still no access to them. Some getters and
> setters for cookies and cookies2 would be nice.
Good idea. I'll throw that in today.
> And by the way, why don't you make some of the fields and methods
> protected so one can easily extend from your classes. Now I have to
> rewrite the entire class or modify the sources directly.
It's hard to be perfect in anticipating where everyone will want to extend
the class hierarchies. I think the code usually tries to err on the side of
added "safety", so private is much more common than protected. There would
probably be more use of protected if Java had borrowed the C++ meaning of
the modifier, rather than opening protected up to the whole package.
So, the approach generally taken is to change the modifier from private to
protected during a refactoring that makes it necessary. If it would benefit
you to have some particular method(s) changed so you can subclass, post it
to the list. Better yet, post your extension to the list as a patch so that
we can all benefit from your work.
Scott Nichol
>
> Best regards,
> Remus Stratulat
>
>
> On Tue, 2002-07-09 at 16:10, Scott Nichol wrote:
> > What you say is true of the latest release, but the current source,
> > available through the nightly distribution or CVS tree, supports
multiple
> > cookies.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Remus Stratulat" <rs...@interakt.ro>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, July 09, 2002 4:56 AM
> > Subject: cookies
> >
> >
> > > Will be a version with support for multiple cookies and cookie
handling?
> > >
> > > Right now in SOAPHTTPConnection the responseHeaders can hold only the
> > > last cookie that was set (due to the fact that it's a Hashtable). I
know
> > > that the SOAP's main goal is not session maintaining but I'm
confronting
> > > with this problem. Along with this, an interface for accessing the
> > > cookieHeader and cookieHeader2 is necessary as some of us need to work
> > > with the cookies. Right now I will deal with this on my own as I can
but
> > > out there might be others that don't have the time or will to modify
> > > your source code.
> > >
> > > Best regards,
> > > Remus Stratulat
> > >
> > >
> > > --
> > > /**
> > > * Remus Stratulat - KrysalIDE maintainer
> > > * InterAkt Online.
> > > *
> > > * @phone +40 90 07 24 07
> > > * @email rstratulat@interakt.ro
> > > * @web http://www.interakt.ro
> > > */
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> --
> /**
> * Remus Stratulat - KrysalIDE maintainer
> * InterAkt Online.
> *
> * @phone +40 90 07 24 07
> * @email rstratulat@interakt.ro
> * @web http://www.interakt.ro
> */
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: cookies
Posted by Remus Stratulat <rs...@interakt.ro>.
Ok, I got it. Thank you. But still no access to them. Some getters and
setters for cookies and cookies2 would be nice.
And by the way, why don't you make some of the fields and methods
protected so one can easily extend from your classes. Now I have to
rewrite the entire class or modify the sources directly.
Best regards,
Remus Stratulat
On Tue, 2002-07-09 at 16:10, Scott Nichol wrote:
> What you say is true of the latest release, but the current source,
> available through the nightly distribution or CVS tree, supports multiple
> cookies.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Remus Stratulat" <rs...@interakt.ro>
> To: <so...@xml.apache.org>
> Sent: Tuesday, July 09, 2002 4:56 AM
> Subject: cookies
>
>
> > Will be a version with support for multiple cookies and cookie handling?
> >
> > Right now in SOAPHTTPConnection the responseHeaders can hold only the
> > last cookie that was set (due to the fact that it's a Hashtable). I know
> > that the SOAP's main goal is not session maintaining but I'm confronting
> > with this problem. Along with this, an interface for accessing the
> > cookieHeader and cookieHeader2 is necessary as some of us need to work
> > with the cookies. Right now I will deal with this on my own as I can but
> > out there might be others that don't have the time or will to modify
> > your source code.
> >
> > Best regards,
> > Remus Stratulat
> >
> >
> > --
> > /**
> > * Remus Stratulat - KrysalIDE maintainer
> > * InterAkt Online.
> > *
> > * @phone +40 90 07 24 07
> > * @email rstratulat@interakt.ro
> > * @web http://www.interakt.ro
> > */
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
/**
* Remus Stratulat - KrysalIDE maintainer
* InterAkt Online.
*
* @phone +40 90 07 24 07
* @email rstratulat@interakt.ro
* @web http://www.interakt.ro
*/
Re: cookies
Posted by Remus Stratulat <rs...@interakt.ro>.
Ok, I got it. Thank you. But still no access to them. Some getters and
setters for cookies and cookies2 would be nice.
And by the way, why don't you make some of the fields and methods
protected so one can easily extend from your classes. Now I have to
rewrite the entire class or modify the sources directly.
Best regards,
Remus Stratulat
On Tue, 2002-07-09 at 16:10, Scott Nichol wrote:
> What you say is true of the latest release, but the current source,
> available through the nightly distribution or CVS tree, supports multiple
> cookies.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Remus Stratulat" <rs...@interakt.ro>
> To: <so...@xml.apache.org>
> Sent: Tuesday, July 09, 2002 4:56 AM
> Subject: cookies
>
>
> > Will be a version with support for multiple cookies and cookie handling?
> >
> > Right now in SOAPHTTPConnection the responseHeaders can hold only the
> > last cookie that was set (due to the fact that it's a Hashtable). I know
> > that the SOAP's main goal is not session maintaining but I'm confronting
> > with this problem. Along with this, an interface for accessing the
> > cookieHeader and cookieHeader2 is necessary as some of us need to work
> > with the cookies. Right now I will deal with this on my own as I can but
> > out there might be others that don't have the time or will to modify
> > your source code.
> >
> > Best regards,
> > Remus Stratulat
> >
> >
> > --
> > /**
> > * Remus Stratulat - KrysalIDE maintainer
> > * InterAkt Online.
> > *
> > * @phone +40 90 07 24 07
> > * @email rstratulat@interakt.ro
> > * @web http://www.interakt.ro
> > */
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
/**
* Remus Stratulat - KrysalIDE maintainer
* InterAkt Online.
*
* @phone +40 90 07 24 07
* @email rstratulat@interakt.ro
* @web http://www.interakt.ro
*/
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
What you say is true of the latest release, but the current source,
available through the nightly distribution or CVS tree, supports multiple
cookies.
Scott Nichol
----- Original Message -----
From: "Remus Stratulat" <rs...@interakt.ro>
To: <so...@xml.apache.org>
Sent: Tuesday, July 09, 2002 4:56 AM
Subject: cookies
> Will be a version with support for multiple cookies and cookie handling?
>
> Right now in SOAPHTTPConnection the responseHeaders can hold only the
> last cookie that was set (due to the fact that it's a Hashtable). I know
> that the SOAP's main goal is not session maintaining but I'm confronting
> with this problem. Along with this, an interface for accessing the
> cookieHeader and cookieHeader2 is necessary as some of us need to work
> with the cookies. Right now I will deal with this on my own as I can but
> out there might be others that don't have the time or will to modify
> your source code.
>
> Best regards,
> Remus Stratulat
>
>
> --
> /**
> * Remus Stratulat - KrysalIDE maintainer
> * InterAkt Online.
> *
> * @phone +40 90 07 24 07
> * @email rstratulat@interakt.ro
> * @web http://www.interakt.ro
> */
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: cookies
Posted by Scott Nichol <sn...@scottnichol.com>.
What you say is true of the latest release, but the current source,
available through the nightly distribution or CVS tree, supports multiple
cookies.
Scott Nichol
----- Original Message -----
From: "Remus Stratulat" <rs...@interakt.ro>
To: <so...@xml.apache.org>
Sent: Tuesday, July 09, 2002 4:56 AM
Subject: cookies
> Will be a version with support for multiple cookies and cookie handling?
>
> Right now in SOAPHTTPConnection the responseHeaders can hold only the
> last cookie that was set (due to the fact that it's a Hashtable). I know
> that the SOAP's main goal is not session maintaining but I'm confronting
> with this problem. Along with this, an interface for accessing the
> cookieHeader and cookieHeader2 is necessary as some of us need to work
> with the cookies. Right now I will deal with this on my own as I can but
> out there might be others that don't have the time or will to modify
> your source code.
>
> Best regards,
> Remus Stratulat
>
>
> --
> /**
> * Remus Stratulat - KrysalIDE maintainer
> * InterAkt Online.
> *
> * @phone +40 90 07 24 07
> * @email rstratulat@interakt.ro
> * @web http://www.interakt.ro
> */
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>