Search Results for "call"

...The main purpose of RestSharp is to make synchronous and asynchronous calls to remote resources over HTTP. As the name suggests, the main audience of RestSharp are developers who use REST APIs. However, RestSharp can call any API over HTTP (but not HTTP/2), as long as you have the resource URI and request parameters that you want to send comply with W3C HTTP standards. RestSharp can take care of serializing the request body to JSON or XML and deserialize the response. It can also form a valid request URI based on different parameter kinds.

Most modern networking is built either on slow and ambiguous REST APIs or unnecessarily complex gRPC. FastAPI, for example, looks very approachable. We aim to be equally or even simpler to use. It takes over a millisecond to handle a trivial FastAPI call on a recent 8-core CPU. In that time, light could have traveled 300 km through optics to the neighboring city or country, in my case. How does UCall compare to FastAPI and gRPC? How can a tiny pet-project with just a couple thousand lines of code compete with two of the most established networking libraries? UCall stands on the shoulders of Giants.

...The http service can be used globally Vue.http or in a Vue instance this.$http. A Vue instance provides the this.$http service which can send HTTP requests. A request method call returns a Promise that resolves to the response. Also the Vue instance will be automatically bound to this in all function callbacks. Shortcut methods are available for all request types. These methods work globally or in a Vue instance. The Recipes provide code examples to common use-cases. If you want to share your recipe feel free to send a pull request.

...The body of the Request is built using the RequestBuilder @resultBuilder. It merges each RequestParam in the body into one CombinedParam object. This contains all the other params as children. When you run .call(), the children are filtered to find the Url, and any other optional parameters that may have been included.

This is a tiny Go package that wraps HTTP handlers to transparently gzip the response body, for clients which support it. Although it's usually simpler to leave that to a reverse proxy (like nginx or Varnish), this package is useful when that's undesirable. Call GzipHandler with any handler (an object which implements the http.Handler interface), and it'll return a new handler which gzips the response.

...This library will fetch your swagger schema, convert it to a GraphQL schema and convert GraphQL parameters to REST parameters. From there you are control of making the actual REST call. This means you can reuse your existing HTTP client, use existing authentication schemes and override any part of the REST call. You can override the REST host, proxy incoming request headers along to your REST backend, add caching etc.

...Let's take a large linear data stream, split it into variable-sized chunks (the size of each being a function of the chunk's contents), and store these chunks in individual, compressed files in some directory, each file named after a strong hash value of its contents, so that the hash value may be used to as key for retrieving the full chunk data. Let's call this directory a "chunk store". At the same time, generate a "chunk index" file that lists these chunk hash values plus their respective chunk sizes in a simple linear array. The chunking algorithm is supposed to create variable, but similarly sized chunks from the data stream.

This is a SAP addon to handle JSON data within SAP ABAP Programs. It comes in the customer exchange namespace /CEX/ and has to be installed as an SAP transport request. The addon supports object oriented JSON methods to process deep structured JSON data. Building JSON data from SAP data objects and parsing JSON data back to SAP data objects are supported. See the WIKI for some examples. Thanks to the SAP community and especially to Rüdiger Plantiko for the basic work...