Linked by Thom Holwerda on Thu 28th Oct 2010 20:07 UTC, submitted by poundsmack
Permalink for comment 447548
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2007-09-22
I couldn't find anything in the Harmony-project SVN which made me think this came from there.
Not in incubator either.
So the license at the top is a mistake, atleast.
Maybe someone ran a tool to place such a license at the top of files which didn't have anything yet...?
The code from Google and Oracle/Sun looks very similar, their is definitely a common origin. The quesion obviously is, what is the origin. It could have been generated based on some specification for the x509-certificate that this deals with.
But the creator (or person that imported the source into the Android git repository) should be able to point out where it came from.
Or completely the other way around, there might be a test-suite which tried to use this API and they created a similair API because it was needed to pass some tests.
Edited 2010-10-28 23:35 UTC