Why not
require 'xmlrpc/client'
@server = XMLRPC::Client.new((secure) ? MY_SECURE_URN : MY_URN,
MY_ENDPOINT, nil, nil, nil, nil, nil, secure)
@server.call('my.method.name', {:id => 1, :area => 'someplace'}
etc.
I've had nothing but good results from xmlrpc. Any reason not to use it?
On Feb 23, 2009, at 7:03 PM, Sarah Mei wrote:
>
> erb. Set up a boilerplate file and fill in what you need. It's MUCH
> faster than trying to generate it with REXML.
>
> On Mon, Feb 23, 2009 at 6:57 PM, Don French <[email protected]> wrote:
>>
>> I have a mashup I need to d with a site that uses xmlrpc. I am trying
>> to understand the the call method. I have the following items that
>> need to be passed to the remote site.
>>
>> methodName
>> and the following structure
>> ID - string
>> area - string
>> views = array of strings
>>
>> I know what the xml should look like
> [...lots of xml...]
>>
>> I have results from various inputs from the view for the value. I am
>> trying to figure out how to create the xml structure and how to use
>> it
>> in the XMLRPC call.
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
