My current XML-RPC implementation is done using
servlet-to-servlet communication (running in TomCat).
Now I need to implement XML-RPC on
SSL.
I have downloaded JSSE and configured SSL
support on TomCat.
But what changes should I make to my XML-RPC
codes?
Can anyone provide some sample code
If you must use HTTP then building streaming over
XML-RPC as Paul suggests is an appropriate thing to
do. If HTTP isn't necessarily mandated then you should
investigate BEEP, www.beepcore.org, as a mechanism for
defining a protocol that meets your application's bulk
data transfer requirements.
..
Isn't this simply something like the VM name or OS name, version,
hostname or anything such ?? That would be my guess.
Paul
On Mercredi, mars 6, 2002, at 09:42 , Lin, Yaxiong wrote:
>
> Lucas:
>
> Thanks for the explanation. But I was using apache's xmlrpc package on
> both
> the client sid
No, no, no and no !
(I should be make some nuances though)
The XML-RPC specification experessedly specify that the Content-Length
of the XML-RPC message is part of the header so, unless you are doing it
in special cases where you would know the size in advance (and would
then need to modify th
Lucas:
Thanks for the explanation. But I was using apache's xmlrpc package on both
the client side and the server side. Why would the client (apache xmlrpc
client) create different header (and longer than 512) when runs on IBM zOS
while it runs ok (identical .jar file) on NT?
Thanks.
- Yaxio
Yaxiong,
It is not wise to emit a header longer than 512 bytes, because many server
implementations will choke. At one time, I believe in HTTP 1.0, the max was
255, and there are still many servers that will use that limit. Unless you can
guarantee that the receiving server will always be of yo
Oh my, of course: we're not even doing anything useful with those headers!
Thanks John.
Hannes
John Wilson wrote:
>Hannes,
>
>I have a small buffer for the header and just throw away any bytes that
>don't fit in. The only headers I'm interested in for XML-RPC are not going
>to be long so I
"John Wilson" <[EMAIL PROTECTED]> writes:
> - Original Message -
> From: "Alain K" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, March 06, 2002 4:44 PM
> Subject: Byte Streaming
>
>
>> Hello,
>>
>> Is it possible to send large data via xmlrpc without
>> loading everythi
"Stuart Roll" <[EMAIL PROTECTED]> writes:
> Hannes -
>
> Of course that sets a static variable so you can only have one kind of
> encoding at a time per JVM. That should be okay for most, I would think,
> but it could be more flexible.
Stuart, I totally agree. Patches anyone?
Hannes,
I have a small buffer for the header and just throw away any bytes that
don't fit in. The only headers I'm interested in for XML-RPC are not going
to be long so I don't care about the very long ones.
This seems to me to be a slightly more robust approach.
John Wilson
The Wilson Part
- Original Message -
From: "Alain K" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 06, 2002 4:44 PM
Subject: Byte Streaming
> Hello,
>
> Is it possible to send large data via xmlrpc without
> loading everything into memory first using some kind
> of streaming mecani
any chanace we can get one?
Hello,
Is it possible to send large data via xmlrpc without
loading everything into memory first using some kind
of streaming mecanism.
Thanks for your help.
Alain.
___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yah
Yaxiong,
I'm sorry I can't put the current code up for download. You have two
options:
- Get it via anonymous CVS as described here
http://xml.apache.org/cvs.html
- Or just make the modification to the 1.0 distribution (just replace
512 with 2048 twice - when the byte array is instanciated
Hannes:
I have never used CVS myself. Do I need to wait till the next built or is
there a distribution zip file I can download?
Thanks.
- Yaxiong
> -Original Message-
> From: Hannes Wallnöfer [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, March 06, 2002 9:56 AM
> To: [EMAIL PROTECTED]
I just increased the buffer size from 512 to 2048 bytes. If you use the
latest version from the CVS, you shouldn't see this error again (unless
your client sends some abnormally large HTTP header).
Hannes
Lin, Yaxiong wrote:
>I am getting the "HTTP Header too long" error on the WebServer (ru
You will really have to debug I fear.
In the output you print I didn't see any header, was there really non ??
That looks real weird !
Paul
On Mercredi, mars 6, 2002, at 04:06 , Lin, Yaxiong wrote:
>
> Paul:
>
> The garbled text I attached was printed to my xmlrpc WebServer console
> running o
Paul:
The garbled text I attached was printed to my xmlrpc WebServer console
running on NT with debug=true set. On IBM zOS, I ran:
java -classpath d:\MarsServer\xmlrpc.jar org.apache.xmlrpc.XmlRpcClient
http://R0086529:8083 mars.runMARSCommand "get_statistics(|text|)"
What do I need to do to
A zip is now also available under
http://www.activemath.org/~ilo/revisions/xmlrpc/
I am not too sure if this can influence the garbled text which seems to
come from the header. Did you try debugging things so as to see when
this bit has come (before or after header end ?). As of http r
Kurt,
Good, I think the encoding-specification through setEncoding should
still work, though I did not test if and, of course, at the possible
risk that your string contains non-encodable characters.
If the encoding has been specificied with XmlRpc.setEncoding then it
should work. Well... it
Hannes:
I am not technical enough in this area to make a suggestion on the header
length limit. I will leave this to those who are more technically talented
people than me to contribute.
Thanks.
- Yaxiong
> -Original Message-
> From: Hannes Wallnöfer [SMTP:[EMAIL PROTECTED]]
> Sent:
Hannes -
Of course that sets a static variable so you can only have one kind of
encoding at a time per JVM. That should be okay for most, I would think,
but it could be more flexible.
Stuart
Kurt Ward wrote:
>Paul,
>
>This is great! We have the need to send UTF-8 encoded strings
>to an app
Kurt Ward wrote:
>Paul,
>
>This is great! We have the need to send UTF-8 encoded strings
>to an application and feel that SOAP is a little overkill for
>what we are trying to do. Hopefully this can get worked into
>CVS.
>
>One suggestion though: I would like to have the option of specifying
>t
Paul:
Is this (encoding) something can be specified as a system property?
Also, is it possible that you can make zip file available?
Do you know if this would solve my problem of xmlrpc client sending some
garbled text in the header to my xmlrpc server (webserver app) on NT, as
below:
Paul,
This is great! We have the need to send UTF-8 encoded strings
to an application and feel that SOAP is a little overkill for
what we are trying to do. Hopefully this can get worked into
CVS.
One suggestion though: I would like to have the option of specifying
the encoding.
Thanks!
Kurt
Hi there,
Since a while happy users of the Helma XML-RPC library we have made a
few patches.
Two things that seem important for everyone and one that was important
only for us:
-> we wanted to have the ability to exchange UTF-8 encoded messages so
the XMLWriter has been enriched and the Min
Obviously the 512 byte limit is to short.
Any idea what a good assumption would be for the maximum size of a
single HTTP header?
1k? 2k?
Hannes
Lin, Yaxiong wrote:
>I am getting the "HTTP Header too long" error on the WebServer (running on
>NT) when processing request from the client runing o
27 matches
Mail list logo
