るりまサーチ

最速Rubyリファレンスマニュアル検索!
36件ヒット [1-36件を表示] (0.227秒)

別のキーワード

  1. new openssl::bn
  2. new openssl::cipher.ciphers
  3. new openssl::asn1::asn1data
  4. new openssl::pkey::ec::group
  5. new openssl::x509::certificate

検索結果

XMLRPC::Client#call2(method, *args) (39139.0)

The difference between this method and XMLRPC::Client#call is, that this method do ((*not*)) raise a XMLRPC::FaultException exception. The method returns an array of two values. The first value indicates if the second value is a return-value (true) or an object of type XMLRPC::FaultException. Both are explained in XMLRPC::Client#call.

...and XMLRPC::Client#call is, that
this method do ((*not*)) raise a XMLRPC::FaultException exception.
The method returns an array of two values. The first value indicates if
the second value is a return-value (true) or an object of type
XMLRPC::FaultException.
Both are explained in XMLRPC::Client#cal...
...l.

Simple to remember: The "2" in "call2" denotes the number of values it returns....

XMLRPC::Client#multicall2(*methods) (27148.0)

Same as XMLRPC::Client#multicall, but returns like XMLRPC::Client#call2 two parameters instead of raising an XMLRPC::FaultException.

...Same as XMLRPC::Client#multicall, but returns like XMLRPC::Client#call2 two parameters
instead of raising an XMLRPC::FaultException....

XMLRPC::Client#call2_async(...) (27101.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#multicall2_async(...) (27101.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#call_async(...) (24001.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

絞り込み条件を変える

XMLRPC::Client#multicall_async(...) (24001.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#proxy2_async(...) (24001.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#proxy_async(...) (24001.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client (23064.0)

Class XMLRPC::Client provides remote procedure calls to a XML-RPC server.

...Class XMLRPC::Client provides remote procedure calls to a XML-RPC server.

After setting the connection-parameters with XMLRPC::Client.new which
creates a new XMLRPC::Client instance, you can execute a remote procedure
by sending the XMLRPC::Client#call or XMLRPC::Client#call2
message to this new in...
...icate which method to
call on the remote-side and of course the parameters for the remote procedure.

require "xmlrpc/client"

server = XMLRPC::Client.new("www.ruby-lang.org", "/RPC2", 80)
begin
param = server.call("michael.add", 4, 5)
puts "4 + 5 = #{param}"
rescue XMLRP...
...rror:"
puts e.faultCode
puts e.faultString
end

or

require "xmlrpc/client"

server = XMLRPC::Client.new("www.ruby-lang.org", "/RPC2", 80)
ok, param = server.call2("michael.add", 4, 5)
if ok then
puts "4 + 5 = #{param}"
else
puts "Error:"
puts pa...

XMLRPC::Client#proxy2(prefix, *args) (21064.0)

Almost the same like XMLRPC::Client#proxy only that a call on the returned XMLRPC::Client::Proxy object behaves like XMLRPC::Client#call2, i.e. a call on that object will return two parameters.

...Almost the same like XMLRPC::Client#proxy only that a call on the returned
XMLRPC::Client
::Proxy object behaves like XMLRPC::Client#call2, i.e.
a call on that object will return two parameters....

絞り込み条件を変える

XMLRPC::Client::Proxy.new(server, prefix, args=[], meth=:call, delim=".") (3018.0)

Creates an object which provides method_missing.

...des method_missing.

server must be of type XMLRPC::Client, which is the XML-RPC server to be used
for a XML-RPC call. prefix and delim will be prepended to the methodname
called onto this object.

Parameter meth is the method (call, call2, call_async, call2_async) to use for
a RPC.

args are argume...

xmlrpc/client (42.0)

XML-RPC クライアントのためのライブラリです。

...イアントのためのライブラリです。

require "xmlrpc/client"

# Make an object to represent the XML-RPC server.
server = XMLRPC::Client.new( "xmlrpc-c.sourceforge.net", "/api/sample.php")

# Call the remote server and get our result
result = server.call("sample.sumAndDiffere...
...==== by catching a XMLRPC::FaultException exception

require "xmlrpc/client"

# Make an object to represent the XML-RPC server.
server = XMLRPC::Client.new( "xmlrpc-c.sourceforge.net", "/api/sample.php")

begin
# Call the remote server and get our result
result = server.call("sample...
...==== by calling "call2" which returns a boolean

require "xmlrpc/client"

# Make an object to represent the XML-RPC server.
server = XMLRPC::Client.new( "xmlrpc-c.sourceforge.net", "/api/sample.php")

# Call the remote server and get our result
ok, result = server.call2("sample.sumAndDif...