But simple http CAN stream !
http 1.1 even can recover broken streams.
Just... xml-rpc cannot.
Because you can do it on top (and do recovery as well).
Paul
On Jeudi, mars 7, 2002, at 12:56 , ward harold wrote:
> If you must use HTTP then building streaming over
> XML-RPC as Paul suggests is an
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.
..
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
"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,
>
- 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 fi
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
