I-Client elungiselelwe ayinawo umthelela ku-ClientResource esasebenzisa enye i-connector. Ku-helper ye-org.restlet.ext.httpclient ye-Restlet 2.4.4, xhuma i-resource kulelo client ngaphambi kokuyiqala:

Client connector = new Client(new Context(), Protocol.HTTPS);
connector.getContext().getParameters().set("proxyHost", "proxy.example");
connector.getContext().getParameters().set("proxyPort", "8080");

ClientResource resource = new ClientResource(
    "https://service.example/status");
resource.setNext(connector);
connector.start();
try {
    String body = resource.get().getText();
} finally {
    resource.release();
    connector.stop();
}

I-setNext(connector) iyindawo yokuxhuma. I-context isebenzisa okhiye ababhalwe phansi be-proxyHost ne-proxyPort be-helper, kanti i-hostname ihlukene ne-scheme ne-port yayo. Zisethe ngaphambi kwe-connector.start(). Ku-HTTP endpoint yomphakathi, lezi zinkambu ezimbili zithatha ikheli ne-port ohlwini lwe-HTTP proxy.

Lokhu kucabanga ukuthi i-helper esetshenzisiwe iyisandiso se-Apache esishiwo. Ingathola futhi izinto ezimisiwe ku-JVM http.proxyHost ne-http.proxyPort; amanani e-context acacile enza i-endpoint yale connector ibonakale.

Isibonelo sisebenzisa i-text body, sikhulula i-resource futhi simise i-connector. Ukusetshenziswa kwe-streaming nakho kufanele kusebenzise noma kukhulule i-representation yako ukuze izixhumanisi ze-pool zikhululwe.

Izihloko ezihlobene