Re: Socket inheritance: A tale of two vendors
- From: Chuck Dillon <spam@xxxxxxxxxxxxx>
- Date: Wed, 07 Dec 2005 08:44:32 -0600
googlegroups@xxxxxxxxxx wrote:
So, my questions are:
> 2) Does it sound like I've got a clear grasp of the problem, or is > there some other possibility I've overlooked?
Are you within the margins in how you use the software? If the vendors aren't interested in fixing the problem it could mean they don't acknowledge that there is a problem. That they consider you outside of their operational expectations or otherwise abusing their software. If you are in the margins then the fault lies with you and you aren't asking for a fix you are asking for a favor.
1) Does the blame lie equally with both vendors, or is one of them slightly more wrong?
Assuming you are between the margins. If B's API and docs provide a mechanism to handle your scenario and A failed to utilitze it the fault is with A. Otherwise, B assumes responsibility for the functionality provided by their API and the fault is with them.
-- ced
Many thanks for opinions on the matter.
/chris marget
-- Chuck Dillon Senior Software Engineer NimbleGen Systems Inc. .
- Follow-Ups:
- Re: Socket inheritance: A tale of two vendors
- From: googlegroups
- Re: Socket inheritance: A tale of two vendors
- References:
- Socket inheritance: A tale of two vendors
- From: googlegroups
- Socket inheritance: A tale of two vendors
- Prev by Date: Re: definition of terminal, et cetera
- Next by Date: Re: finding holes in the program
- Previous by thread: Re: Socket inheritance: A tale of two vendors
- Next by thread: Re: Socket inheritance: A tale of two vendors
- Index(es):
Relevant Pages
|