|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
things that make you go hmmm.....
Providing API code, and then offering low royalty payments to those who implement it seems like another way to sell something. Would the royalties paid would be enough to reduce competetion?
Truly open would mean not charging for use of published APIs themselves. It would be fair game if they charged for CALs for connections to a database or other server.
This appears to be a sneaky way to steer clear of antitrust implications. The proper response would be to decrease price on client software and charge more for CALs, and give away the API.
Does anyone have a better idea?