but it seems like big overkill for me to have Apache running CGI script which "embeds" www client which requests data from other apache instance.
You say overkill, I say classic application stack. For the past quarter century or so we've been working to a greater or lesser extent with this setup where the user/client/browser interacts with the web server(s), behind which is the application server(s), behind which is the data source(s). There are other ways for sure but this is by far the most common basic setup I have seen across many installations. You already have the backend sorted by the sound of it so adding the lightweight front end should not be "overkill".
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
