[PEPr] +1 for Web Services::Services_LiveJournal
| From: | Justin Patrin | Date: | Fri, 12 Nov 2004 18:30:51 +0000 |
| Subject: | [PEPr] +1 for Web Services::Services_LiveJournal | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34364@lists.php.net to get a copy of this message | ||
Justin Patrin (http://pear.php.net/user/justinpatrin) has voted +1 on the proposal for Web
Services::Services_LiveJournal.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=86
Vote information:
http://pear.php.net/pepr/pepr-vote-show.php?id=86&handle=justinpatrin
This vote is conditional. The condition is:
Sorry to give you all this now, I should have done this before voting.
- Spaces around the '=' in function declarations.
- as keyword in foreach() should be lowercase
- postEntry should raise a PEAR_Error when posting fails
- fetchEntry should raise a PEAR_Error when fetching fails
- fetchEntries shouldn't have a print_r() in it
- fetchEntry does this: is_array($response['events'][0]) but $response may be null
- postEntry checks if $response !== 0, but _callMethod() returns null if the response is 0. Is this
correct?
- _xmlToArray should raise a PEAR_Error when it doesn't understand the type to let the caller
know that somehting went wrong
- _callMethod should raise a PEAR_Error when calling the method fails (this is optional, it's a
design choice, but I suggest you pass up any XML_RPC messages)
- fetchEntries shoudl check for an error from _callMethod and pass it up
- above errors should also give the reason for failure
--
Sent by PEPr, the automatic proposal system at http://pear.php.net