Difference between revisions of "BaSyx / Documentation / API / Gateway"
< BaSyx | Documentation | API
m (Daniel.Espen.iese.fraunhofer.de moved page BaSyx.Gateway.API to BaSyx / Documentation / API / Gateway: Consistency) |
m (Updates top links) |
||
| Line 1: | Line 1: | ||
{| class="wikitable" | {| class="wikitable" | ||
| − | | [[ | + | | [[BaSyx_/_Documentation_/_Gateway | Overview]] <nowiki>|</nowiki> [[BaSyx_/_Documentation_/_API_/_Gateway | Interface]] <nowiki>|</nowiki> [[BaSyx_/_Documentation_/_Implementation_/_Gateway | Implementation]] |
|} | |} | ||
| + | |||
Since a Gateway translates between protocols, the API is dependent on the translated protocols. Thus, there is no specific API. | Since a Gateway translates between protocols, the API is dependent on the translated protocols. Thus, there is no specific API. | ||
For example, an HTTP-GET is internally translated to the VAB primtive ''GET'' and then further translated to the native protocol equivalent of a ''GET''. | For example, an HTTP-GET is internally translated to the VAB primtive ''GET'' and then further translated to the native protocol equivalent of a ''GET''. | ||
Latest revision as of 10:05, 12 March 2020
| Overview | Interface | Implementation |
Since a Gateway translates between protocols, the API is dependent on the translated protocols. Thus, there is no specific API. For example, an HTTP-GET is internally translated to the VAB primtive GET and then further translated to the native protocol equivalent of a GET.