Turn tracing on for all connections to the specified HTTP server. Turn tracing OFF for all connections to the specified HTTP server. Turn tracing off for the ibrowse process. Tell ibrowse to stream the next chunk of data to the caller. Tell ibrowse to close the connection associated with the specified stream. Terminate a worker process spawned using spawn_worker_process/2 or spawn_link_worker_process/2. Starts the ibrowse process linked to the calling process. Starts the ibrowse process without linking. Same as spawn_worker_process/1 but takes as input a Host and Port instead of a URL. Same as spawn_worker_process/2 except the the calling process is linked to the worker process which is spawned.Ĭreates a HTTP client process to the specified Host:Port which is not part of the load balancing pool. Same as spawn_worker_process/1 except the the calling process is linked to the worker process which is spawned. Shows some internal information about load balancing to a Shows some internal information about load balancing. Set the maximum number of connections allowed to a specific Host:Port. Set the maximum pipeline size for each connection to a specific Host:Port. Same as send_req/6 except that the first argument is the PID returned by spawn_worker_process/2 or spawn_link_worker_process/2. Same as send_req/5 except that the first argument is the PID returned by spawn_worker_process/2 or spawn_link_worker_process/2. Same as send_req/4 except that the first argument is the PID returned by spawn_worker_process/2 or spawn_link_worker_process/2. Same as send_req/3 except that the first argument is the PID returned by spawn_worker_process/2 or spawn_link_worker_process/2. This is the basic function to send a HTTP request. The functions to call are send_req/3, send_req/4, send_req/5, send_req/6.Ĭlear current configuration for ibrowse and load from the file nf in the IBROWSE_EBIN/./priv directory. The ibrowse process also determines which connection to pipeline a certain request on. Multiple connections to a webserver are setup based on the settings for each webserver. There is one process to handle one TCP connection to a webserver (implemented in the module ibrowse_http_client). There is one load balancing process per unique webserver. There is one named process called ‘ibrowse’ which assists in load balancing and maintaining configuration. This module implements the API of the HTTP client. The ibrowse application implements an HTTP 1.1 client in erlang. The ibrowse application implements an HTTP 1.1 client in erlang.Ĭopyright © 2005-2012 Chandrashekhar MullaparthiĪuthors: Chandrashekhar Mullaparthi ( chandrashekhar dot mullaparthi at gmail dot com).
0 Comments
Leave a Reply. |