Let's say that I want to send a couple different kinds of
object/record types in a single request. e.g. a new customer and a
couple purchase orders for it.
Assume each record type can be handled like a flat array of name-value
pairs.
How best to do that?
I think of an 'array' as a single-column list of values. A 'struct' as
a flat table (each 'member' being a row); actually, more like single
record, which each 'member' being a name-value pair (field-name and
its value). So if I'm passing multiple flat records, that would be an
array of structs?
So if I want to send a couple different types of records, with
multiple instances of 1 of those types, I might have...
* an array to represent passing multiple object types
* a value for each type
* a single struct for the single record of one type
* an array of structs for multiple records of a single type
Does this make sense? I've read a fair number of documents, but
they're all rather simple in structure. Is the next level of data
model complexity documented anywhere with some decent explanations
and/or examples?
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xml-rpc/
<*> To unsubscribe from this group, send an email to:
xml-rpc-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|