Lauyoyin Oracle sun kwatanta sake aiwatar da API ɗin Java a cikin Android tare da kwafin abubuwan da ke cikin "Harry Potter", pdf

Kotun kolin Amurka za ta saurari wani muhimmin shari'a a farkon wannan shekara. Oracle vs Google, wanda zai ƙayyade matsayin doka na API a ƙarƙashin dokar mallakar fasaha. Idan kotu ta goyi bayan Oracle a cikin karar ta na biliyoyin daloli, za ta iya dakile gasa tare da tabbatar da rinjayen manyan masu fasaha, mai yiwuwa har da Google da kanta.

A lokaci guda kuma, an fara gina kasuwancin Oracle akan aiwatar da yaren shirye-shiryen SQL wanda IBM ya haɓaka, kuma har yanzu kamfanin yana ba da sabis na girgije tare da API daga Amazon S3, kuma wannan gaba ɗaya al'ada ce. API ɗin sake aiwatarwa ya kasance wani yanki na halitta na haɓaka kimiyyar kwamfuta tun farkon masana'antar.

Oracle ya zargi Google da yin kwafin Java API ba bisa ka'ida ba, gami da jerin sunayen umarni da aka danganta da tsarin nahawu. Tsarin aiki na Android ya dace musamman da Java API don sauƙaƙa wa masu shirye-shiryen Java don canja wurin software da ilimi zuwa sabon dandamali. Don yin wannan, Android ta kwafi daidai umarnin Java API da tsarin nahawu. shaida Oracle shine cewa irin wannan "sake aiwatarwa" na API ɗin Java ana iya kwatanta shi da kwafin aikin marubuci, kamar littafin wallafe-wallafen "Harry Potter" (wannan. misali na gaske da lauyoyin Oracle suka bayar), da Google ya keta haƙƙin mallaka na Oracle akan sunaye da tsarin umarni API na Java.

Amma APIs ɗin Java ba su ne API ɗin kaɗai ba, kuma Android ba ita ce kawai sake aiwatarwa ba. A cikin masana'antar IT ta yau, APIs suna cikin ko'ina, kuma sakewa yana da mahimmanci don kiyaye gasa don hana manyan kamfanoni yin amfani da su. tunani Charles Duane darekta ne na fasaha da manufofin ƙididdigewa a Cibiyar R Street.

Duane yana ba da misalin shahararren dandalin ajiya na Amazon S3. Don ba da damar rubutawa da dawo da fayiloli daga S3, Amazon ya haɓaka cikakke, cikakken API don yin hulɗa tare da sabis. Misali, don samun jerin fayilolin da aka ajiye (ListObjects) muna aika umarni na GET wanda ke ƙayyade mai watsa shiri da nau'in sigogi nau'in codeing, ci gaba-alama и x-amz-date. Don yin aiki tare da Amazon S3, dole ne software ta yi amfani da waɗannan da wasu takamaiman sunaye daidai.

GET /?Delimiter=Delimiter&EncodingType=EncodingType&Marker=Marker&MaxKeys=MaxKeys&Prefix=Prefix HTTP/1.1
Host: Bucket.s3.amazonaws.com
x-amz-request-payer: RequestPayer

Amazon shine jagorar bayyanannen jagora a cikin kasuwar sabis na girgije, kuma masu fafatawa suna ba da sake aiwatar da S3 API, yayin da suke yin kwaikwayon sunayen umarni, alamomin sigogi, rubuta prefixes. x-amz, Tsarin nahawu da tsarin gaba ɗaya na S3 API. A wasu kalmomi, duk abin da Oracle ya yi iƙirari yana da haƙƙin mallaka.

Daga cikin kamfanonin da ke ba da kwafin Amazon S3 API akwai akwai kuma ita kanta Oracle. Don dacewa, Amazon S3 Compatibility API yana kwafin abubuwa da yawa na Amazon API, har zuwa alamun x-amz.

Oracle yayi iƙirarin cewa halaccin ayyukansa ya dogara ne akan buɗaɗɗen tushen lasisin Apache 2.0, wanda ke ba da damar kwafi da gyara lamba kyauta. Misali, Amazon SDK don Java Hakanan ya zo tare da lasisin Apache 2.0.

Amma tambayar ita ce ko dokar mallakar fasaha ta shafi abubuwa kamar APIs. Wannan shi ne abin da Kotun Koli ta tantance.

Wanene ya ƙirƙira API?

Kalmar da ra'ayi na "laburare na subroutine" sun fara bayyana a cikin littafin Shirye-shiryen da Matsalolin Coding don Kayan Kayan Lantarki na Lantarki - Sashe na II, Volume III (Cibiyar Ci Gaban Nazarin Jami'ar Princeton, 1948) na Herman Goldstein da John von Neumann. kwafi akan archive.org. Abubuwan da ke cikin juzu'i na uku:

Wannan shi ne bayanin farko na hanyoyin da aka tsara don kwamfutoci masu adana shirye-shirye a cikin ma’adana (a baya wannan babu shi). An rarraba shi ga jami'o'i, wadanda a lokacin suna ƙoƙarin ƙirƙirar na'urorin kwamfuta. Kuma mafi mahimmanci, littafin ya ƙunshi mahimman ra'ayi: yawancin shirye-shiryen za su yi amfani da ayyukan gama gari, kuma ɗakunan karatu tare da abubuwan yau da kullun za su rage adadin sabbin lambar da kurakurai. Maurice Wilkes ya sake inganta wannan ra'ayin kuma ya aiwatar da shi a cikin injin EDSAC, wanda ya sami lambar yabo ta 1967 Turing.

Wurin ɗakin karatu na EDSAC yana gefen hagu

Mataki na gaba shine ƙirƙirar ayyuka masu girma da kuma cikakkun hanyoyin mu'amalar software, kamar yadda Maurice Wilkes da David Wheeler suka yi a cikin Shirye-shiryen Shirye-shiryen don Computer Digital Digital (1951).

Term kanta Matsayin Shirin Aikace-aikace (API) ya bayyana a wani wuri a ƙarshen 60s.

Marubucin gabatarwa "Takaitaccen Tarihin Maudu'i na API" Joshua Block ya ba da misalai da yawa na mu'amalar shirye-shirye, tsarin koyarwa, da ɗakunan karatu na ƙasa: yadda aka ƙirƙira su kuma daga baya aka yi amfani da su. Manufar ita ce sake amfani da ita shine ma'anar API. Wannan shi ne abin da aka halicce su da shi tun farko. Kuma masu haɓakawa koyaushe suna samun damar kwafi da sake yin APIs na wasu mutane:

API
Mahalicci
Shekara
Sake aiwatarwa
Shekara

FORTRAN library
IBM
1958
Univac
1961

IBM S/360 ISA
IBM
1964
Amdahl Corp. girma
1970

Standard C Library
AT&T/Bell Labs
1976
Mark Williams Co., Ltd.
1980

Kira tsarin Unix
AT&T/Bell Labs
1976
Mark Williams Co., Ltd.
1980

Saukewa: VT100ESC
Dec
1978
Heathkit
1980

IBM PC BIOS
IBM
1981
Fasaha ta Phoenix
1984

MS-DOS CLI
Microsoft
1981
Aikin FreeDOS
1998

Hayes AT umarni saitin
Hayes Micro
1982
Anchor Automation
1985

PostScript
Adobe
1985
GNU/GhostScript
1988

SMB
Microsoft
1992
Samba Project
1993

Win32
Microsoft
1993
Aikin Wine
1996

Java 2 dakunan karatu
Lah
1998
Google/Android
2008

API ɗin Yanar Gizo Mai Dadi
Delicious
2003
Fati
2009

source: "Takaitaccen Tarihin Maudu'i na API"

Kwafi da sake amfani da APIs (dakunan karatu, tsarin koyarwa) ba daidai ba ne kawai, amma ana ba da shawarar wannan dabarar shirye-shirye kai tsaye a cikin canons na kimiyyar kwamfuta. Tun kafin yin kwafin musaya na shirye-shiryen S3, Oracle da kansa ya yi hakan sau da yawa. Bugu da ƙari, an fara gina kasuwancin Oracle akan aiwatar da yaren shirye-shirye na SQL wanda IBM ya haɓaka. Samfurin alamar farko na Oracle shine DBMS, wanda aka kwafi akasari daga IBM System R. A wannan yanayin, muna magana ne game da sake aiwatar da SQL a matsayin “misali API” na DBMS.

Ƙaddamar da haƙƙin mallakar fasaha akan APIs na iya ƙirƙirar filin naki na doka wanda ke shafar kowa. APIs aiwatar da sauran ayyukan girgije. Yawancin matakan fasaha, kamar Wi-Fi da ka'idojin Intanet, sun haɗa da APIs. Dole ne a sake aiwatar da hanyoyin sadarwa na shirye-shirye ta wani nau'i akan kowace kwamfuta da uwar garken da ke Intanet. Ka'idar haƙƙin mallaka ta Oracle na iya sa kusan duk abin da kuke yi da kwamfutarku ta haramtacciyar hanya.

Don guje wa waɗannan sakamako masu nisa, Oracle da kotun ƙararrakin da suka tabbatar da hujjojinta sun yi ƙoƙarin iyakance keta haƙƙin mallaka zuwa wasu abubuwan sake aiwatar da API waɗanda ba su dace da asali ba. Amma sake aiwatar da wani bangare kuma sun zama ruwan dare gama gari. Ko da a cikin kwafin S3 API ɗinsa, Oracle ya lura da “bambance-bambance” da yawa da rashin jituwa tare da ainihin APIs na Amazon.

Babban haɗari na ƙarar Oracle shine cewa zai iya hana ƙananan kamfanonin fasaha ƙirƙirar nau'ikan tsarin da suka dace da manyan dandamali kamar S3. Idan ba tare da irin wannan dacewa ba, masu shirye-shirye za su kasance da kyau a kulle su daga abubuwan da wannan kamfani ke bayarwa.

Wakilan masana'antu da masu haɓakawa na iya fatan cewa dalili zai yi nasara a nan, kuma alkalai sun san tushen shirye-shirye.

source: www.habr.com