Function proxy and uri are very poorly named.
proxy and uri are methods
It can easily make people think that it is the server
Not likely, but the documentation definitively clears up what the method does.
, should be called endpoint as it is perceived in the entire SOAP world.
Thats a good suggestion to make to the developers.
uri is hardly needed, but all examples in SOAP::Lite doc have that
The docs say otherwise: Nothing is specified by default and your call will definitely fail if you don't specify the required uri.
you really cannot easily guess what should be passed in..
Why would you guess when you can read the documentation which explains it?
We've all been frustrated, but this kind of module review is not productive.
You should talk to the developers.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | | ** The third rule of perl club is a statement of fact: pod is sexy. |
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
