Using method builders, you are able to prepare an action call by repeatedly calling it’s methods. The server to indicate either the set parts of the request or the desired parts in the response. Most optionals are are considered Parts which are identifiable by name, which will be sent to Optionals are used to indicate that partial requests are responses Optional Parts in Server-RequestsĪll structures provided by this library are made to be encodable andĭecodable via json. The delegate trait is default-implemented, allowing you to customize it with minimal effort. Respective methods will be called to provide progress information, as well as determine whether the system should Method Builder before making the final doit() call. You may alter the way an doit() method is called by providing a delegate to the The distinctiveness of each is represented by customizedĭoit(.) methods, which are then named upload(.) and upload_resumable(.) respectively. Methods supporting uploads can do so using up to 2 different protocols: To trigger a media download, you will have to set up the builder by making

You can see it as meta-data for the actual media. If such a method also supports a Response Result, it will return that by default.

If a method supports downloads, the response body, which is part of the Result, should be Makes the system potentially resilient to all kinds of errors. When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. Hub Delegate, or the Authenticator Delegate.

The doit() methods, or handed as possibly intermediate results to either the Use translate2::', res),Īll errors produced by the system are provided either as Result enumeration as return value of Use translate2::api::DetectLanguageRequest Generally speaking, you can invoke Activities like this:Įxtern crate google_translate2 as translate2

primary types that you can apply Activities toĪll structures are marked with applicable traits to further categorize them and ease browsing.

a central object to maintain state and allow accessing all Activities.

The API is structured into the following primary items: Not what you are looking for ? Find all other Google APIs in their Rust documentation index. Handle the following Resources with ease from the central hub … This documentation was generated from Translate crate version 4.0.1+20170525, where 20170525 is the exact revision of the translate:v2 schema built by the mako code generator v4.0.1.Įverything else about the Translate v2 API can be found at the

Google translate api v2