Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

BaSyx / Documentation / VAB / HTTP Mapping

< BaSyx ‎ | Documentation ‎ | VAB
Revision as of 02:00, 5 August 2020 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
See also TCP Mapping JSON Serialization Exceptions

The following table illustrates the mapping of VAB communication operations to HTTP REST communication that was used in this example. Short values, e.g. the path to the element and an operation ID are transmitted in the header, while complex objects, e.g. parameters are transmitted in the HTTP body, which has no size limitation.


VAB operation HTTP/REST mapping
retrieve(e,p) HTTP-GET e/p
update(e,p,v) HTTP-PUT e/p [body: v as JSON]
create(e,n,v) HTTP-POST e/n [body: v as JSON]
delete(e,p) HTTP-DELETE e/p
invoke(e,p,par) HTTP-POST e/p [body: par as JSON]

Back to the top