Re: Re: [PEPr] Comment on Web Services::Services_urlTea
| From: | Chuck Burgess | Date: | Tue, 09 Oct 2007 13:17:32 +0000 |
| Subject: | Re: Re: [PEPr] Comment on Web Services::Services_urlTea | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-48249@lists.php.net to get a copy of this message | ||
On 10/9/07, Arnaud Limbourg <arnaud@limbourg.com> wrote:
>
> That can be a another step. Experience shows that trying to design
> top-level first does not work that well :)
>
True ;)
I was just broaching the subject to be sure Joe had it in mind going
forward. He's built two Service implementations now, and usually I'll start
looking at a potential interface when I've built a second or third
implementation of something similar (I'm doing that now with a file transfer
interface, with SCP and SFTP implementations to start with).
If each of his next implementations (you are making more, right Joe ;)
intentionally uses the same API calls by proactive design, then it will be
easier to later wrap an interface around them all. Otherwise, it would mean
BC breaks in the API just to build the interface.
I wasn't meaning do the interface now :P That would slow down getting this
second implementation accepted.--
CRB
Let me introduce you to my very own DMCA-protected encryption key:
BC 1B 64 4A 8D DE 49 E8 C3 7D CC EE 1A AD EE F5
(compliments of Freedom-to-Tinker http://www.freedom-to-tinker.com/?p=1155)