headers
Budiman Evan | 1 May 2004 03:33
Picon
Favicon

DXMLRPC Version 2.0.0


Halo,

do you have any papper (explanation about the program) about DXMLRPC Version 2.0.0?

thank u.

		
---------------------------------
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs 

[Non-text portions of this message have been removed]

 
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 <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
Permalink | Reply | 1 comment |
headers
Immo Wache | 2 May 2004 01:01
Picon

Re: DXMLRPC Version 2.0.0

Hi,

unfortunately not :-(

Best way to understand the code use is to look for the examples in
the demos and tests folders. If you be in question for some functions
read the source which comes with the library.

You can mail me if you still have a special question or simply
use this list.

Greetings,
Immo

At 18:33 30.04.2004 -0700, you wrote:

>Halo,
>
>do you have any papper (explanation about the program) about DXMLRPC 
>Version 2.0.0?
>
>
>
>thank u.

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/xml-rpc/
(Continue reading)

Permalink | Reply | 0 comments |
headers
webmaster | 3 May 2004 22:39
Picon

New Message: ? about the spec...

A new message was posted:

Address: http://www.xmlrpc.com/discuss/msgReader$2594

By: Kristian Thy (thy <at> it.edu)

In the spec, it is stated that the &lt;methodName> element contains a string restricted to the following
characters: "identifier characters, upper and lower-case A-Z, the numeric characters, 0-9,
underscore, dot, colon and slash."

What exactly are the "identifier characters"?

 
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 <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
Permalink | Reply | 0 comments |
headers
Bill Seitz | 3 May 2004 23:07
Picon
Favicon

multiple <param> tags?

Is there a good example somewhere of how/when to use multiple <param>
tags in a request (or response)?

 
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 <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
Permalink | Reply | 0 comments |
headers
Bill Seitz | 3 May 2004 23:21
Picon
Favicon

sending multiple record types in a request - how?

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?
(Continue reading)

Permalink | Reply | 3 comments |
headers
greger.ohlson | 4 May 2004 09:06
Picon

RE: sending multiple record types in a request - how?


Hi Bill,

Unless i misinterpret you, it sound like you should be able to
solve your problem using nested structs where your interface
documentation describes the contents of each struct. The top-
level struct represents the "message" with subordinated structs
arrays or primitives containing the actual data in your message:

{
    "anArrayOfPrimitives" : [ "data", 42, 12.5 ],
    "aSinglePrimitive" : "a string for instance",
    "anArrayOfStructs" : [ { "member1" : "data", "member2" : "more data" },
                           { "member1" : "d-a-t-a", "member2" : "more d-a-t-a } ]
}

That is, you can nest your structs and arrays to any level you
want. Just make sure your documentation describes what can be found
under each member of the struct, and they should be able to
navigate your message which essentially becomes a tree of values.
This should be possible using any implementation of the protocol.

In Java for instance, arrays often resolve to java.util.List instances
that can contain structs which resolve to java.util.Map in most
implementations.

Regards,
Greger Ohlson.

-----Original Message-----
(Continue reading)

Permalink | Reply | 1 comment |
headers
webmaster | 4 May 2004 15:32
Picon

New Message: Passing java objects

A new message was posted:

Address: http://www.xmlrpc.com/discuss/msgReader$2595

By: venkataramana (venkat_r_m <at> pune.tcs.co.in)

Hi,
As I went through XML-RPC Specification, I understood data in the form of struct can be sent as parameters.
Since struct can also contain fields which are again of struct type, so that is recursive as Spec says. Does
this mean any java object which has leaf fields of types specified by XML-RPC can be passed as parameters ???

( I understand since Java class fields are either references/primitiveValues so a byte copy of a Java
object is just a shallow copy and not a deep copy.)

Thanks
~Venkat

 
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 <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bill Seitz | 4 May 2004 18:36
Picon
Favicon

Re: sending multiple record types in a request - how?

Thanks.

I came to the realization last night that for most people like me it
just makes sense to play with the available libraries, rather than
trying to understand the spec.

For my case, I (in PyThon):

* started out with a tuple of dictionaries

* each dictionary's key was the record/object type

* if only a single instance of a type was allowed to be passed, then
that dictionary value would be a dictionary

* if multiple instances of a certain type might be passed together,
then the value of that dictionary would be a tuple of dictionaries

http://webseitz.fluxent.com/wiki/XmlRpc

--- In xml-rpc <at> yahoogroups.com, <greger.ohlson <at> m...> wrote:
> 
> Hi Bill,
> 
> Unless i misinterpret you, it sound like you should be able to
> solve your problem using nested structs where your interface
> documentation describes the contents of each struct. The top-
> level struct represents the "message" with subordinated structs
> arrays or primitives containing the actual data in your message:
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gervas Douglas | 5 May 2004 12:47
Favicon

Next-Generation Middleware

RPC and other middleware paradigms such as MOM, DCOM and CORBA have 
given sterling service for more than a decade now.  Wouldn't it be 
great if we could improve on them so that they became automatically 
adaptable as our application structure changes?  Well, perhaps the 
answer can be found in an article in the Inquirer e-magazine which 
also offers a free software download. You can find this article at 
the link below:

http://www.theinquirer.net/?article=15197 

Gervas

 
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 <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
Permalink | Reply | 1 comment |
headers
John Wilson | 5 May 2004 12:59
Picon

Re: Next-Generation Middleware [administrivia]


Sorry about this bit of SPAM. The user has now been permanently banned 
from this mailing list.

John Wilson (Moderator)
The Wilson Partnership
http://www.wilson.co.uk

 
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 <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
Permalink | Reply | 0 comments |

Gmane