cluberti, on Feb 23 2008, 01:19 AM, said:
The problem I have with this, is that it's forcing a company to open it's secrets to the world without compensation. I know people feel different ways about "secret" APIs, but this is a slippery slope - forcing a closed-source company to open it's API's and source seems dangerous to me (even for the EU).
What secrets?
Look at ADS, its an implementation of LDAP, where the Windows file sharing is an implementation of CIFS/SMB. Neither of those protocols originated from Microsoft. They just "enhanced" them until other people (look at SAMBA) can only be compatible with it by re-engineering.
And now someone took the big stick and hit them on their fingers to make them play fair.
Which enables other participiants in the market to be compatible with Windows servers and clients.
Oh and its not for free. If you had read the articles, you'd have seen that any commercial implementation needs to pay a bit of its revenue to MS.
http://www.itnews.com.au/News/63623,eu-for...atent-dogs.aspx
Quote
... In addition to the royalty-free licence for open source developers, Microsoft also reduced the fees it charges commercial vendors of both closed and open source software. The developer will cut its patent licensing fees for commercial vendors from 5.95 per cent to 0.4 per cent of software revenues.
Fees for Microsoft's non-public interoperability information will be reduced to a one-time payment of €10,000. Microsoft had originally demanded 2.98 per cent of revenues. ...
So, now Microsoft will get a bit more competition, and they still get money out of that, unless the competition thinks MS patents aren't wort anything.
As customer you can choose what you like. If you use a 100% MS environment, you got one company to blame. Now if you choose some Linux distribution for the servers for example, worst case your Linux vendor and Microsoft keep blaming eachother if something acts up. But it will still be competition for MS and may have an influence on their price tags. Which should be good for customers.
BTW: Here is the link to the protocol specs.
http://msdn2.microso...y/cc203350.aspx
This post has been edited by bj-kaiser: 24 February 2008 - 04:03 AM