Microsoft immediately wanted more time, and asked for it in a less than polite fashion. Holding true to their word, eEye released the details of the vulnerability in an advisory to the public as scheluded, along with links to Microsoft's timely patch. In seven days, Microsoft was able to assess the problem, release their own advisory and create a working patch with regression testing. Had eEye not held firm on their intended release date, Microsoft would have taken as much time as possible before releasing a patch. Since their initial dealings with Microsoft, eEye has received nothing but quick and courteous responses.
Response time is down to hours compared to days.
Someone must have sent an internal memo. Because of their diligence in releasing vital information to the public on their time schedule and managing the expectations of the software vendor, eEye's policy on full disclosure has lead to a more responsive, open and attentive software vendor. Looking at a history of vendor released security advisories, a pattern emerges that suggests a firm stance on public dissemination of vulnerability information has its merits. Comparing a vendor like Sun Microsystems, we see no pattern of continued releases despite new vulnerabilities brought to light each month on full disclosure security mail lists. Sure seems like it.