Explicit routing

Not sure that "explicit routing" is the right phrase, but what I want to
be able to do (I am seeking help with) is...

[ In case it helps, there's a diagram of this setup at
http://www.lowth.com/pic1.gif .. ]

I have a Linux server (192.168.0.10) that is connected to a network
192.168.0.0/24.

The network has two routers that are both connected to the public
internet and have "home network" addresses 192.168.0.1 and 192.168.0.201
respectively.

A WEB service application on the server trawls large volumes of
information from RSS feeds (etc) from a wide range of IPs on the public
internet while responding to client WEB requests (originating from the
Internet).

The incoming web requests arrive from the internet via the router with
internal address 192.168.0.1 but I want to arrange that the RSS trawl
performed in response to the request goes out (for load balancing
reasons) via the 192.168.0.201 router.

One way that works [but not very well] is to call "route add IP gw
192.168.0.201" before making the connection for the outbound trawl, but
this is inefficient and causes routing table bloat in the long term.

So - is there some way for an application to tell linux to route via a
specific next hop for a particular socket connection without having to
clutter up the "public" routing table?

Thanks.

Chris

--
http://www.lowth.com/rope/BlockingBittorrent
Controlling Bittorrent traffic with a linux firewall, iptables
and ROPE.