Brian Quinlan (brian@...) wrote:
> --- !yaml.org/^rpc-method-call
> method-name: pow
> - 2
> - 3
> --- ^yaml.org/^rpc-method-call
> method-name: format
> string: >
> Late afternoon is best.
> Backup contact is Nancy
> Billsmer @ 338-4338.
> wrap : 79
> justification: right
Why not seperate the named method parameters technique into a seperate
type? !yaml.org,2002/rpc-method-call and !yaml.org,2002/rpc-named-call
or something to that effect. Not a big deal. And don't forget the
dates with domain types soon to be added to the spec.
Personally, I'd rather put the method in the type family and
go with the succinct:
Late afternoon is best.
Backup contact is Nancy
Billsmer @ 338-4338.
Of course, you can't really extend it and add options beyond the
paramaters. But it's also kind of nice to have that restriction
there. Keeps it simple.
I have thought of putting together a simple RPC spec with the
name OKAY (Object Kit Across Yaml; also simply because Okay is
a great word for communciation, synonymous with ACK). If we could
negotiate a subdomain at yaml.org, we could add !okay/call and
!okay/call-named... Yeah, so... A couple ideas.
> def pow(x, y): __builtins__['pow'](x,y)
> def format(string, wrap=80, justification="left",
> use_tabs = 0, spaces_per_tab = 4, use_hyphens = 1):
> raise ValueError, "right justification is not currently
> --- !yaml.org/^rpc-response 6
> --- !yaml.org/^rpc-fault
> fault-message: >
> ValueError: right justification is not currently supported
> Key features:
> - Boxcarred requests are supported by having multiple YAML documents in
> the same HTTP request
Your above example shows a response, followed by a fault. What if the
fault occurs first? Do the other calls continue to roll through? Your
above example implies that both calls are processed, regardless of the
I can see a use in having boxcarred requests fail when any fault is
thrown. Especially if the two requests are closely related.
> I'd like a bit of feedback and advice before I proceed. Is my YAML
> reasonable? Should I differentiate between exceptions and responses
> using an explicit transfer? Does the Python YAML implementation support
> explicit transfers?
For OO languages, the explicit transfer is nicer. PyYaml does support