Archive of UserLand's first discussion group, started October 5, 1998.

Encodings; was Re: XML-RPC Spec Comments

Author:Bob Atkinson
Posted:1/29/1999; 1:42:43 PM
Topic:XML-RPC Spec Comments
Msg #:2574 (In response to 2563)
Prev/Next:2573 / 2575

Small comments:

I really like the simplicity of layout in the existing parameter format; indeed, I'd push to make the 99% case of straightforward invocation even less verbose than at present. So REQUIRING additional tags I think would be an issue.

At the same time, I agree with the need for a hook to allow for multiple encodings over time. Here is my thought on how to do that.

Modify to allow it to alternately contain an element rather than it's normal sequence. would contain a (a URI) and elements. The following, for example, might be an embedded NDR invocation:


  
    uuid:8a885d04-1ceb-11c9-9fe8-08002b104860
    aG93IG5vdyBicm93biBjb3cNCg==

However we do it, I really think we need to be clear about the syntax passed by the caller; having the server guess I don't think is appropriate. Using different URLs causes layering problems in implementations: this is an issue of parameter / result encoding, not object identity. Similarly, forcing the encoding declaration into the transport makes it difficult in implementations to keep track of it reliably at the point in time when you're actually doing the unmarshalling.

I really think the right way of doing it it is some (optional) tag in the block, of which the above is just one possible example.

There are responses to this message:

This page was archived on 6/13/2001; 4:47:39 PM.

© Copyright 1998-2001 UserLand Software, Inc.