From: Martin Hart Date: 2002-12-12T07:22:32+09:00 Subject: Re: Problems transporting nil values using XMLRPC (net/http ?) On 12/11/02, 3:36:17 AM, Stefan Arentz wrote regarding Re: Problems transporting nil values using XMLRPC (net/http ?): > Don't forget that NIL/NULL values are not part of the XML-RPC > spec. I know that some implementations support them, but since > there is no official way to pass them, your code could break > when used with other servers or clients. Ah, I didn't know that - I'd better go and read the spec :-) Given that I ought not to be doing this as it is "non-standard", I can see only two solutions: 1. Don't send null values - rely on the fact that if a value is "missing" then it is NULL. 2. Encode null values in some other way - e.g. "*NULL*" - which is really messy and will likely break :-) 1 looks best but unfortunately breaks a load of existing test cases :-( I am not all that hot on this rpc type technology. Can anybody see any alternatives (perhaps some other protocol supports the transportation of null values SOAP ??) TIA -- Martin Hart Tel: +44 (0) 1582 618468 Arnclan Fax: +44 (0) 1582 619596 Union Street, E-mail: martin@zsdfherg.com Dunstable, Beds LU6 1EX