I think implementation here really depends on the use cases for your system.
Thinking of Apache as a kernel and innumerable web browsers as agents, Apache creates a pre-forked server design and assigns each agent request to a single child process. This load balances and implicitly assumes that all child processes are equivalent in capability. A caching proxy server would give priority to the fast cache implementation first, and would only assign a slow main database lookup second.
Without knowing more about your problem, I would recommend prioritizing implementations according to time and space usage, picking the cheapest available inplementation first. If there are to be many implementations sitting at the same URL, arrange for the kernel to spawn a processes like Apache to handle just one agent request per child process and keep listening for others. You will better be able to manage kernel performance if it is the kernel that is managing service requests, not the agents.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.