phpxmlrpc-devel — Discussion list for developers on XML-RPC for PHP

[phpxmlrpc-devel] Fault: Code: 2

[Gautam J. <GJ...@gr...>]

Hi,
I m trying to implement a webservice in php. I m using xmlrpc.inc and
xmlrpcs.inc.
I tested the client/server sample implementations and i got this error:

Fault: Code: 2 Reason 'Invalid return payload: enabling debugging to examine
incoming payload'
XML error: junk after document element at line 2 

how do i deal with this error?

Thanks
Gautam.

[phpxmlrpc-devel] debugging info extension

[Gaetano G. <giu...@se...>]

Could it be be a good idea to move xmlrpc_debugmsg into the server =
class, using a property for storing debug string info rather than a =
global variable?
It surely would allow to create 2 instances of the server class and use =
them at the same time [altough I know no real use for it!]

Besides, it could be useful to add the xmlrpc_debugmsg function to the =
client, too. This would lead to a cleaner implementation of debug info, =
making it uniform between client & server (right now the server has =
xmlrpc_debugmsg, while the client has setDebug, and the msg only has the =
debug property but no access methods).

The downside is, of course, breaking the API...
the big problem I see is that the functions registered by the server do =
not have a pointer to the server instance itself at the moment (except =
for system. functions), so calling a method of the server is unfeasable =
:(

Bye, Gaetano

[phpxmlrpc-devel] Problems with ISO8859-1 encoding

[Gaetano G. <giu...@se...>]

I broke xmlrpc response parsing when enabling debug mode on the server =
and sending a comment including chars =A9 and =AE (hope they show off ok =
in the mail: ALT+0169 and ALT+0174).

My best guess is I have to specify the encoding of the xml msg as =
ISO-8859-1, either 1) in the <?xml?> tag within the answer msg, or 2) =
with an http 'charset' header.

I tried method 1 (patching the server code), and it did not work.
Then, peering at the client code I found out that global variable =
$xmlrpc_defencoding is used to create the XML parser. I did not try yet =
overriding it, but I guess it would do.

Now, my questions are:

- looking at HTTP1.1 spec (RFC2616) I understood that HTTP requests of =
type TEXT/XXX SHOULD(?) be treated as ISO-8859-1 encoded when an =
encoding charset is omitted. So, unless the XML (or XML-RPC) spec =
dictates otherwise, the default $xmlrpc_defencoding should be changed =
??? (I know xml states that only UTF-8 and UTF-16 encoding MUST be =
supported...)

- why not make this global variable a property of the xmlrpcmsg class? =
It looks more reasonable to me: both the server and client should be =
able to support seamlessly messages using different encodings.
The client should then try to get the encoding used in the message, =
before instantiating the xmlparser object, from: a) the HTTP HEADER, b) =
the <?XML?> tag, or some combination thereof strategy (I'm not too sure =
of my understanding of protcol specs...)

- the encoding type could be added to the response string of the =
xmlrpcserver class, also using an xmlrpc_encoding property

Thanks, Gaetano

[phpxmlrpc-devel] patch now is really working.

[maHo <lu...@ma...>]

	see 2 last forwarded mails on the list.

maHo

[phpxmlrpc-devel] Re: xmlrpc for php bug(and patch)

[Edd D. <ed...@us...>]

On Tue, 2002-09-24 at 19:22, maHo wrote:
> and anther mistake. my patch doesn't work. dont even look at this. but 
> the bug is still the same, and is serious. i'll try to fix the patch and 
> i'll be sending :))
> 
> maHo
> 

OK.  It might be best to continue this discussion on the developer's
mailing list -- you can join up from the sourceforge page.  That way the
other folks working on this can help out.

-- Edd

[phpxmlrpc-devel] [Fwd: Re: xmlrpc for php bug(and patch)]

[Edd D. <ed...@us...>]

[phpxmlrpc-devel] [Fwd: Re: xmlrpc for php bug(and patch)]

[Edd D. <ed...@us...>]

[phpxmlrpc-devel] [Fwd: xmlrpc for php bug(and patch)]

[Edd D. <ed...@us...>]

Miles, do you want to take a look at this and check the bits that you
think appropriate into CVS?

-- Edd

Re: [phpxmlrpc-devel] pear

[Edd D. <ed...@us...>]

It used to be in PEAR (although it was added without communicating with
us at all, and when I tried communicating with the PEAR folk I didn't
have a good experience.)

If it has been removed since then, it is probably because of the C
extension for XML-RPC in PHP4 and folk thinking there's no need for
duplicates.

On Mon, 2002-09-23 at 03:49, Ryan Hoegg wrote:
> As someone with no say and no code contributed so far, I would still 
> like to submit my +0.000005.
> 
> I have occasional projects in PHP and I always go to the PEAR stuff first.
> 
> --
> Ryan Hoegg
> ISIS Networks  
> 
> Andres Salomon wrote:
> 
> >Do folks think it would be worth the effort to try and get this xmlrpc
> >implementation in php's standard PEAR distribution?  I'm willing to help
> >the code adhere to the PEAR coding convention, if so.
> >
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpxmlrpc-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpxmlrpc-devel

Re: [phpxmlrpc-devel] pear

[Ryan H. <rh...@is...>]

As someone with no say and no code contributed so far, I would still 
like to submit my +0.000005.

I have occasional projects in PHP and I always go to the PEAR stuff first.

--
Ryan Hoegg
ISIS Networks  

Andres Salomon wrote:

>Do folks think it would be worth the effort to try and get this xmlrpc
>implementation in php's standard PEAR distribution?  I'm willing to help
>the code adhere to the PEAR coding convention, if so.
>

[phpxmlrpc-devel] pear

[Andres S. <dil...@vo...>]

Do folks think it would be worth the effort to try and get this xmlrpc
implementation in php's standard PEAR distribution?  I'm willing to help
the code adhere to the PEAR coding convention, if so.


-- 
Buying a Unix machine guarantees you a descent into Hell. It starts when
you plug the computer in and it won't boot. Yes, they really did sell you
a $10,000 computer with an unformatted disk drive.
	-- Philip Greenspun

Re: [phpxmlrpc-devel] Interoperability

[Ryan H. <rh...@is...>]

Hi,

Yoiu are right.  This is an issue with XML-RPC 1.1.  My changes to the 
XML-RPC client software are being done specifically to add this 
functionality.  I was reminded and have verified that chunking breaks 
the XML-RPC spec because of the requirement for a valid Content-Length 
header.  However, I still want to use it.

I will report success or failure when I get this done.

Ryan Hoegg
ISIS Networks

Edd Dumbill wrote:

>OK, I figured this out.  Your request header has HTTP/1.1 in it.  If
>that's what you send, that's what the web server expects you to speak!  
>
>The ones your program worked against worked because they don't implement
>HTTP/1.1.
>
>Change your request to HTTP/1.0, or implement HTTP/1.1 properly :)
>
>-- Edd
>
>On Wed, 2002-09-18 at 08:45, Edd Dumbill wrote:
>  
>
>>Hey Ryan,  looks like my Apache on xmlrpc.usefulinc.com is speaking
>>HTTP/1.1, using the chunked encoding.  ie. it's not actually wrong per
>>HTTP, but it is wrong per the XML-RPC spec.  I'll have to look into why
>>this is happening, some config issue I suspect.
>>
>>Meanwhile it's trivial to set up a demo server on a machine of your own,
>>just unpack the distribution and install the demo files.
>>
>>On Fri, 2002-09-13 at 21:53, Ryan Hoegg wrote:
>>    
>>
>>>Hi,
>>>
>>>I am a user and rare contributor to the Apache group's XML-RPC library 
>>>(http://xml.apache.org/xml-rpc).  I am upgrading the HTTP client in our 
>>>code and decided to test against a server that is running your code. 
>>> Because the new HTTP client code is more strict in its interpretation 
>>>of the server's response, we are unable to access XML-RPC servers using 
>>>your code.  A link to the posts to the xml-rpc-dev mailing list at 
>>>apache, where you can find a list of other sites that exhibited similar 
>>>behavior:
>>>http://marc.theaimsgroup.com/?l=rpc-dev&m=103176693403852&w=2
>>>http://marc.theaimsgroup.com/?l=rpc-dev&m=103179721532649&w=2
>>>
>>>What follows is a transcript of a session, which I executed manually.
>>>
>>>Cheers,
>>>Ryan Hoegg
>>>ISIS Networks
>>>
>>>$ telnet xmlrpc.usefulinc.com 80
>>>Trying 80.87.131.124...
>>>Connected to usefulinc.com.
>>>Escape character is '^]'.
>>>POST /demo/server.php HTTP/1.1
>>>User-Agent: ISIS Networks/0.2b (WinNT)
>>>Host: xmlrpc.usefulinc.com:80
>>>Content-Type: text/xml
>>>Content-length: 211
>>>
>>><?xml version="1.0" 
>>>encoding="ISO-8859-1"?><methodCall><methodName>examples.addtwo</methodName><params><param><value><int>12</int></value></param><param><value><int>11</int></value></param></params></methodCall> 
>>>
>>>HTTP/1.1 200 OK
>>>Date: Wed, 11 Sep 2002 17:17:29 GMT
>>>Server: Apache/1.3.26 (Unix) Debian GNU/Linux PHP/4.2.2
>>>X-Powered-By: PHP/4.2.2
>>>Transfer-Encoding: chunked
>>>Content-Type: text/xml
>>>Content-length: 121
>>>
>>>79
>>><?xml version="1.0"?>
>>><methodResponse>
>>><params>
>>><param>
>>><value><int>23</int></value>
>>></param>
>>></params>
>>></methodResponse>
>>>0
>>>
>>>Connection closed by foreign host.
>>>$
>>>

Re: [phpxmlrpc-devel] Interoperability

[Edd D. <ed...@us...>]

OK, I figured this out.  Your request header has HTTP/1.1 in it.  If
that's what you send, that's what the web server expects you to speak! =20

The ones your program worked against worked because they don't implement
HTTP/1.1.

Change your request to HTTP/1.0, or implement HTTP/1.1 properly :)

-- Edd

On Wed, 2002-09-18 at 08:45, Edd Dumbill wrote:
> Hey Ryan,  looks like my Apache on xmlrpc.usefulinc.com is speaking
> HTTP/1.1, using the chunked encoding.  ie. it's not actually wrong per
> HTTP, but it is wrong per the XML-RPC spec.  I'll have to look into why
> this is happening, some config issue I suspect.
>=20
> Meanwhile it's trivial to set up a demo server on a machine of your own,
> just unpack the distribution and install the demo files.
>=20
> On Fri, 2002-09-13 at 21:53, Ryan Hoegg wrote:
> > Hi,
> >=20
> > I am a user and rare contributor to the Apache group's XML-RPC library=20
> > (http://xml.apache.org/xml-rpc).  I am upgrading the HTTP client in our=
=20
> > code and decided to test against a server that is running your code.=20
> >  Because the new HTTP client code is more strict in its interpretation=20
> > of the server's response, we are unable to access XML-RPC servers using=
=20
> > your code.  A link to the posts to the xml-rpc-dev mailing list at=20
> > apache, where you can find a list of other sites that exhibited similar=
=20
> > behavior:
> > http://marc.theaimsgroup.com/?l=3Drpc-dev&m=3D103176693403852&w=3D2
> > http://marc.theaimsgroup.com/?l=3Drpc-dev&m=3D103179721532649&w=3D2
> >=20
> > What follows is a transcript of a session, which I executed manually.
> >=20
> > Cheers,
> > Ryan Hoegg
> > ISIS Networks
> >=20
> > $ telnet xmlrpc.usefulinc.com 80
> > Trying 80.87.131.124...
> > Connected to usefulinc.com.
> > Escape character is '^]'.
> > POST /demo/server.php HTTP/1.1
> > User-Agent: ISIS Networks/0.2b (WinNT)
> > Host: xmlrpc.usefulinc.com:80
> > Content-Type: text/xml
> > Content-length: 211
> >=20
> > <?xml version=3D"1.0"=20
> > encoding=3D"ISO-8859-1"?><methodCall><methodName>examples.addtwo</metho=
dName><params><param><value><int>12</int></value></param><param><value><int=
>11</int></value></param></params></methodCall>=20
> >=20
> > HTTP/1.1 200 OK
> > Date: Wed, 11 Sep 2002 17:17:29 GMT
> > Server: Apache/1.3.26 (Unix) Debian GNU/Linux PHP/4.2.2
> > X-Powered-By: PHP/4.2.2
> > Transfer-Encoding: chunked
> > Content-Type: text/xml
> > Content-length: 121
> >=20
> > 79
> > <?xml version=3D"1.0"?>
> > <methodResponse>
> > <params>
> > <param>
> > <value><int>23</int></value>
> > </param>
> > </params>
> > </methodResponse>
> > 0
> >=20
> > Connection closed by foreign host.
> > $
> >=20
> >=20
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > phpxmlrpc-devel mailing list
> > php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpxmlrpc-devel

Re: [phpxmlrpc-devel] Interoperability

[Edd D. <ed...@us...>]

Hey Ryan,  looks like my Apache on xmlrpc.usefulinc.com is speaking
HTTP/1.1, using the chunked encoding.  ie. it's not actually wrong per
HTTP, but it is wrong per the XML-RPC spec.  I'll have to look into why
this is happening, some config issue I suspect.

Meanwhile it's trivial to set up a demo server on a machine of your own,
just unpack the distribution and install the demo files.

On Fri, 2002-09-13 at 21:53, Ryan Hoegg wrote:
> Hi,
>=20
> I am a user and rare contributor to the Apache group's XML-RPC library=20
> (http://xml.apache.org/xml-rpc).  I am upgrading the HTTP client in our=20
> code and decided to test against a server that is running your code.=20
>  Because the new HTTP client code is more strict in its interpretation=20
> of the server's response, we are unable to access XML-RPC servers using=20
> your code.  A link to the posts to the xml-rpc-dev mailing list at=20
> apache, where you can find a list of other sites that exhibited similar=20
> behavior:
> http://marc.theaimsgroup.com/?l=3Drpc-dev&m=3D103176693403852&w=3D2
> http://marc.theaimsgroup.com/?l=3Drpc-dev&m=3D103179721532649&w=3D2
>=20
> What follows is a transcript of a session, which I executed manually.
>=20
> Cheers,
> Ryan Hoegg
> ISIS Networks
>=20
> $ telnet xmlrpc.usefulinc.com 80
> Trying 80.87.131.124...
> Connected to usefulinc.com.
> Escape character is '^]'.
> POST /demo/server.php HTTP/1.1
> User-Agent: ISIS Networks/0.2b (WinNT)
> Host: xmlrpc.usefulinc.com:80
> Content-Type: text/xml
> Content-length: 211
>=20
> <?xml version=3D"1.0"=20
> encoding=3D"ISO-8859-1"?><methodCall><methodName>examples.addtwo</methodN=
ame><params><param><value><int>12</int></value></param><param><value><int>1=
1</int></value></param></params></methodCall>=20
>=20
> HTTP/1.1 200 OK
> Date: Wed, 11 Sep 2002 17:17:29 GMT
> Server: Apache/1.3.26 (Unix) Debian GNU/Linux PHP/4.2.2
> X-Powered-By: PHP/4.2.2
> Transfer-Encoding: chunked
> Content-Type: text/xml
> Content-length: 121
>=20
> 79
> <?xml version=3D"1.0"?>
> <methodResponse>
> <params>
> <param>
> <value><int>23</int></value>
> </param>
> </params>
> </methodResponse>
> 0
>=20
> Connection closed by foreign host.
> $
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpxmlrpc-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpxmlrpc-devel
--=20
Edd Dumbill ----| phone: +44 1904 427740 fax: +44 8709 909625 |-----
 | Managing Editor, XML.com, XMLhack.com  --  Chair, XML Europe 2002
 | I PGP sign my email; more info at http://heddley.com/edd/pgp.html

Re: [phpxmlrpc-devel] Patches for system.multicall() support.

[Edd D. <ed...@us...>]

Looks good to me, please apply.

I think we should shoot for a new point-release soon, too.

-- Edd

On Fri, 2002-09-06 at 03:32, Miles Lott wrote:
> One question:  Can you provide a proper test method, or show me how you=20
> structure the request?  I need to add something to the testsuite.php to
> verify this is working.
>=20
> That, and pending Edd's approval, is all that is left for me to apply thi=
s.
>=20
> Jeff Dairiki wrote:
> > Hi,
> >=20
> > I've just posted some patches "XML-RPC for PHP" to the SF patch tracker=
.
> > http://sf.net/tracker/index.php?func=3Ddetail&aid=3D605246&group_id=3D3=
4455&atid=3D411302
> >=20
> > The patches add system.multicall() support to both the client and the
> > server.
> > See http://www.xmlrpc.com/discuss/msgReader$1208 for more motivation an=
d
> > docs.
> >=20
> > Best Regards,
> > Jeff Dairiki
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by: OSDN - Tired of that same old
> > cell phone?  Get a new here for FREE!
> > https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
> > _______________________________________________
> > phpxmlrpc-devel mailing list
> > php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpxmlrpc-devel
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
> _______________________________________________
> phpxmlrpc-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpxmlrpc-devel

[phpxmlrpc-devel] Interoperability

[Ryan H. <rh...@is...>]

Hi,

I am a user and rare contributor to the Apache group's XML-RPC library 
(http://xml.apache.org/xml-rpc).  I am upgrading the HTTP client in our 
code and decided to test against a server that is running your code. 
 Because the new HTTP client code is more strict in its interpretation 
of the server's response, we are unable to access XML-RPC servers using 
your code.  A link to the posts to the xml-rpc-dev mailing list at 
apache, where you can find a list of other sites that exhibited similar 
behavior:
http://marc.theaimsgroup.com/?l=rpc-dev&m=103176693403852&w=2
http://marc.theaimsgroup.com/?l=rpc-dev&m=103179721532649&w=2

What follows is a transcript of a session, which I executed manually.

Cheers,
Ryan Hoegg
ISIS Networks

$ telnet xmlrpc.usefulinc.com 80
Trying 80.87.131.124...
Connected to usefulinc.com.
Escape character is '^]'.
POST /demo/server.php HTTP/1.1
User-Agent: ISIS Networks/0.2b (WinNT)
Host: xmlrpc.usefulinc.com:80
Content-Type: text/xml
Content-length: 211

<?xml version="1.0" 
encoding="ISO-8859-1"?><methodCall><methodName>examples.addtwo</methodName><params><param><value><int>12</int></value></param><param><value><int>11</int></value></param></params></methodCall> 

HTTP/1.1 200 OK
Date: Wed, 11 Sep 2002 17:17:29 GMT
Server: Apache/1.3.26 (Unix) Debian GNU/Linux PHP/4.2.2
X-Powered-By: PHP/4.2.2
Transfer-Encoding: chunked
Content-Type: text/xml
Content-length: 121

79
<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value><int>23</int></value>
</param>
</params>
</methodResponse>
0

Connection closed by foreign host.
$

Re: [phpxmlrpc-devel] Patches for system.multicall() support.

[Miles L. <mi...@sp...>]

One question:  Can you provide a proper test method, or show me how you 
structure the request?  I need to add something to the testsuite.php to
verify this is working.

That, and pending Edd's approval, is all that is left for me to apply this.

Jeff Dairiki wrote:
> Hi,
> 
> I've just posted some patches "XML-RPC for PHP" to the SF patch tracker.
> http://sf.net/tracker/index.php?func=detail&aid=605246&group_id=34455&atid=411302
> 
> The patches add system.multicall() support to both the client and the
> server.
> See http://www.xmlrpc.com/discuss/msgReader$1208 for more motivation and
> docs.
> 
> Best Regards,
> Jeff Dairiki
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> phpxmlrpc-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpxmlrpc-devel

[phpxmlrpc-devel] Patches for system.multicall() support.

[Jeff D. <da...@da...>]

Hi,

I've just posted some patches "XML-RPC for PHP" to the SF patch tracker.
http://sf.net/tracker/index.php?func=detail&aid=605246&group_id=34455&atid=411302

The patches add system.multicall() support to both the client and the
server.
See http://www.xmlrpc.com/discuss/msgReader$1208 for more motivation and
docs.

Best Regards,
Jeff Dairiki

[phpxmlrpc-devel] FAQ on XML RPC

[Pascal M. <p.m...@ha...>]

Hi,

I'd like to use XML RPC, and define some services. Where can I found
informations on HOW TO make a server and clietns ?
Regards
Pascal Miquet

Re: [phpxmlrpc-devel] [Fwd: xmlrpc.inc, problem is UTF-8 string]

[Miles L. <mi...@sp...>]

Would it be necessary and/or acceptable to wrap this
in a test for the default encoding?:

    if($xmlrpc_defencoding == 'UTF-8')
    {
        $rs.="<${typ}>" . htmlspecialchars(utf8_encode($val)) .
"</${typ}>";
    }
    else
    {
        $rs.="<${typ}>" . htmlspecialchars($val) . "</${typ}>";
    }

Edd Dumbill wrote:
> 
>   ------------------------------------------------------------------------
> 
> Subject: xmlrpc.inc, problem is UTF-8 string
> Date: Mon, 25 Feb 2002 00:31:52 +0100
> From: "Mr ROYER" <er...@id...>
> Organization: Idée production
> To: <ed...@us...>
> 
> Hi,
> 
> I have change a code in line 872:
> 
>    case $xmlrpcString:
>     $rs.="<${typ}>" . htmlspecialchars(utf8_encode($val)). "</${typ}>";
> 
> I call utf8_encode in this line cause the character in XML  format are in
> UTF-8
> ==> I had problem with accent (a client in delphi) and now it's work fine
> 
> Thanks for your module :)  ==> great thing
> Etienne ROYER

-- 

Miles Lott - phpGroupWare
http://www.phpgroupware.org

[phpxmlrpc-devel] [Fwd: xmlrpc.inc, problem is UTF-8 string]

[Edd D. <ed...@us...>]

[phpxmlrpc-devel] introduction

[Andres S. <dil...@mp...>]

Edd mentioned I should introduce myself to the list, so here goes.  I
work for Voxel, and have taken over the project that Justin Miller
previously worked on.  We use xmlrpc quite extensively in a production
environment.  I requested cvs write access in order to add some sanity
checks to the code; we see a bit too many php errors, messing up xml
responses.  For example, one of the mistakes I accidentally made was
passing xmlrpcval's constructor an associative array, w/ a type of
"array"; it should've been "struct".  Expected behavior would've been to
have some sort of "type mismatch" error (or even just detect the type
automatically); instead, there's a for loop inside one of the serialize
functions that iterates through the array via loop counter, so
uninitialized variables end up being processed as arrays.  My goal is to
improve usability for the programmer; instead of having to trace through
code every time there's a problem, give a reasonable error message
describing incorrect use of the API.

BTW, I notice the code in CVS is indented consistently; I thank whoever
did that. :)


-- 
"I think a lot of the basis of the open source movement comes from
  procrastinating students..."
	-- Andrew Tridgell <http://www.linux-mag.com/2001-07/tridgell_04.html>

[phpxmlrpc-devel] Re: [phpxmlrpc] new stable release, 1.02

[Miles L. <mi...@sp...>]

OK ;)  I am soon to commit this to cvs.  Using your
testsuite.php, I was able to pass the test.  One more
check against comment.php or so and I will be done.

Edd Dumbill wrote:
> 
> A new stable release is available of XML-RPC for PHP
> 
> It should be downloadable shortly from:
> 
> https://sourceforge.net/project/showfiles.php?group_id=34455
> 
> It fixes the issue of the double CR LF bug mentioned today on this list,
> and also a couple of warnings generated by uninitialized variables.
> 
> -- Edd
> 
> PS. other developers: I've *not* merged these changes into unstable, as
> milosch has rewritten the code -- but it still has the same bug.  I did
> add a test into the test suite which shows this bug up, so it shouldn't
> be difficult to fix, just that I'm not going to do it right now :)
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature

-- 

Miles Lott - http://milosch.net
Handspring Visor USB and BeOS FS support for Linux
phpGroupWare - http://www.phpgroupware.org

[phpxmlrpc-devel] new stable release, 1.02

[Edd D. <ed...@us...>]

A new stable release is available of XML-RPC for PHP

It should be downloadable shortly from:

https://sourceforge.net/project/showfiles.php?group_id=3D34455

It fixes the issue of the double CR LF bug mentioned today on this list,
and also a couple of warnings generated by uninitialized variables.

-- Edd

PS. other developers: I've *not* merged these changes into unstable, as
milosch has rewritten the code -- but it still has the same bug.  I did
add a test into the test suite which shows this bug up, so it shouldn't
be difficult to fix, just that I'm not going to do it right now :)

[phpxmlrpc-devel] [Fwd: Re: About PHP and XML RPC]

[Edd D. <ed...@us...>]

A solution.