view release on metacpan or  search on metacpan

README  view on Meta::CPAN

48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
    "$c->req->xmlrpc".
 
    Directly after, it will find out the Path of the Action to dispatch to,
    by splitting methodName by ".":
 
      methodName: hello.world
      path      : /hello/world
 
    From this point, it will dispatch to '/hello/world' when it exists, like
    Catalyst Urls would do. What means: you will be able to set Regexes,
    Paths etc on subroutines to define the endpoint.
 
    We discuss these custom XMLRPC attributes below.
 
    When the request is dispatched, we will return $c->stash->{xmlrpc} to
    the xmlrpc client, or, when it is not available, it will return
    $c->stash to the client. There is also a way of defining $c->stash keys
    to be send back to the client.
 
ATTRIBUTES
    You can mark any method in your Catalyst application as being available

lib/Catalyst/Plugin/Server/XMLRPC.pm  view on Meta::CPAN

58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
an OBJECT containing XMLRPC specific parameters in C<< $c->req->xmlrpc >>.
 
Directly after, it will find out the Path of the Action to dispatch to, by
splitting methodName by C<.>:
 
  methodName: hello.world
  path      : /hello/world
 
From this point, it will dispatch to '/hello/world' when it exists,
like Catalyst Urls would do. What means: you will be able to set Regexes,
Paths etc on subroutines to define the endpoint.
 
We discuss these custom XMLRPC attributes below.
 
When the request is dispatched, we will return $c->stash->{xmlrpc} to the
xmlrpc client, or, when it is not available, it will return $c->stash to
the client. There is also a way of defining $c->stash keys to be send back
to the client.
 
=head1 ATTRIBUTES