|
|
Posted by Mark A. Boyd on 01/21/08 01:42
Jerry Stuckle <jstucklex@attglobal.net> posted in comp.lang.php:
> Mark A. Boyd wrote:
>> Jerry Stuckle <jstucklex@attglobal.net> posted in comp.lang.php:
>>> I will continue to recommend cURL for the reasons I have outlined.
>>> The difference is I have no relationship with cURL, other than as a
>>> user of the library.
>>
>> PMFBI, but I don't understand why you don't see the flexibility offered
>> by Manuel's class.
>
> I see the flexibility. But it's still not as flexible as cURL.
Thanks, that wasn't clear to me from previous posts. Well, you were very
clear about what you thought about cURL.
>> I suspect that most of us are not hired at the consultant level, but as
>> application/Web developers. As such, we likely have much less influence
>> over our clients' decisions about Web server configurations. If a
>> client is paying consultant fees for advice, I would think they are
>> more willing to listen to such advice. When hiring/contracting a Web
>> developer, they are more apt to set the requirements that he/she must
>> comply with.
>
> As a web developer, you are a consultant. And my customers don't set
> the requirements - we discuss them and agree on the requirements. They
> trust my advice, because I have sound reasons for giving them.
Makes sense. Although I envision more situations where it might be difficult
to convince a large client to reconfigure a server.
>> So, if one can build a library of reusable code via the httpClient
>> class that works with/without cURL, well, isn't that flexible?
>
> Sure. But I can do more with cURL than you can with the httpClient
> class.
Understood - when cURL is available.
>> Or are you suggesting that one should develope this library with code
>> to handle either situation oneself? If you were to do that, would you
>> create two separate libraries of code or would you create a class that
>> can handle either situation? (Ponder this question as a developer, not
>> as a higher-paid consultant.)
>
> I didn't say any such thing. The only thing I said was that cURL is
> more flexible. Period. Nothing more.
Thus the second question above. I wouldn't have asked if you had already
answered. AFAIK, only top-posters and Jeopardy players think with the mind-
set of answers first-questions later.
>> Or would you simply turn down jobs that cannot use cURL?
>
> As I said. I negotiate with my customers. I didn't say what I would or
> would not use in any specific situation.
Hmm, I think your answer to the question is "I negotiate with my customers."
Vague, but OK. I'm certainly not trying to pry into your negotiating
techniques.
> I use the tool most suited for the job.
Cliche as this answer may sound, I accept it for the omitted answers. After
all, cliches become cliches for good reason.
--
Mark A. Boyd
Keep-On-Learnin' :)
Navigation:
[Reply to this message]
|