Re: [PEPr] Comment on Networking::Net_TrackBack
| From: | KOYAMA Tetsuji | Date: | Tue, 13 Apr 2004 08:07:46 +0000 |
| Subject: | Re: [PEPr] Comment on Networking::Net_TrackBack | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27530@lists.php.net to get a copy of this message | ||
Hi Greg,
Thanks for your suggestion.
At 13 Apr 2004 04:17:29 -0000,
PEPr wrote:
> Perhaps translateToRSS() should be toRSSXML() in keeping with the
> convention of toHTML() toArray() and so on
>
> pingResult() => getPingXML()
OK, I'll change method names.
> It is unclear which methods should be used for sending trackbacks,
> and which should be used for receiving them. I would recommend
> putting the server ones at the bottom and labelling them.
I think so too. I'll put them bottom.
> I wouldn't use PEAR::throwError() with just error messages, error
> codes are required as well. PEAR::raiseError('Invalid PATH_INFO',
> NET_TRACKBACK_INVALID_PATHINF). I would recommend having a bit more
> verbose error messages
Humm..., I understand but I think it can work with structured error
codes. In existing PEAR packages, the error codes is defined as
package dependent. In order not to be mixed with the error of
HTTP_Request, what error code should be defined?
Regards,
--
koyama@hoge.org
koyama@beatraft.com
KOYAMA Tetsuji BeatCraft, Inc., Tokyo, Japan.