Article delegate-en/4417 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
[Reference:<_A4416@delegate-en.ML_>]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: File Size depended routing. Is it possible?
17 Mar 2009 07:07:13 GMT feedback@delegate.org (Yutaka Sato)
The DeleGate Project


Hi,

In message <_A4416@delegate-en.ML_> on 03/17/09(15:50:28) I wrote:
 |I'm not sure what does "reading" people means, but if you can distinguish
 |them with IP-address or domain or proxy authentication, you can select
 |a route for them with the FORWARD parameter (generalized parameter to
 |select upstream proxies as MASTER, PROXY and SOCKS) as follows for example:
 |
 |  FORWARD="delegate://fast-link-gw:8888-_-*:*:reading-people"
 |  FORWARD="delegate://slow-link-gw:8888-_-*:*:*"
 |  HOSTLIST=reading-people:host1,host2,*.domain1,...

If you can pre-determine which servers have heavy data, you can use
the list of such servers to do routing as this:

  FORWARD="delegate://slow-link-gw:8888-_-*:heavy-servers:*"
  HOSTLIST=heavy-servers:serv1,serv2,...

Another possible solution with the current implementation of DeleGate
as a HTTP proxy is using MOUNT to specify the upstream proxy based on
URL as follows for example.

  MOUNT="http://large-images.dom/img/* = MASTER=slow-link-gw:8888"

Cheers,
Yutaka
--
  9 9   Yutaka Sato <y.sato@delegate.org> http://delegate.org/y.sato/
 ( ~ )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
@_@V