Re: contentLengthOptional really working as documented?

2007-09-27 Thread Andreas Sahlbach
Done. Please see https://issues.apache.org/jira/browse/XMLRPC-148 I fixed the server part. The client part can be fixed by not using sun jdk 1.6 classes but using commons-httpclient classes as transport. This is quite acceptable for me. On 9/24/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > >

Re: contentLengthOptional really working as documented?

2007-09-24 Thread Jochen Wiedmann
On 9/24/07, Andreas Sahlbach <[EMAIL PROTECTED]> wrote: > No guru available? I just want to know what is the official roadmap > regarding streaming. Has it changed away from the documented features or is > it maybe currently unknown? Or is it just a personal problem of my > installation? Any hint

Re: contentLengthOptional really working as documented?

2007-09-24 Thread Andreas Sahlbach
No guru available? I just want to know what is the official roadmap regarding streaming. Has it changed away from the documented features or is it maybe currently unknown? Or is it just a personal problem of my installation? Any hint would be welcome so I can figure out what to do next... Thanks,

contentLengthOptional really working as documented?

2007-09-14 Thread Andreas Sahlbach
Hi xmlrpc-gurus! I am trying to migrate my projects from xmlrpc 2.0 to xmlrpc 3.1. I need to migrate one of the clients and the server, so I am very interested, that this part of the documentation is true: > If streaming mode is disabled, then the server will always behave like a standard XML-RPC