Here's how I've been trying to structure my thinking:
- The apps could live on the server (S), or the client (C).
- The libs could live on the server, or the client.
- The perl executable employed could live on the server, or the client.
- The perl process could run on the client, or on the server.
- The app could be a stand-alone program (P), or a be served as a cgi script (W).
My preference would be S1. I believe C4 and P5 are requirements, given the way the apps use local OLE and run some long processes. My problem has been keeping all the machines up-to-date (eg C2, with ppm & cpan). I've never before considered executing perl locally from networked binaries (C4, S2, S3).
My original idea was to bundle with PAR, so C1 C2 (sort of), C3 C4 and P5 (clearly).
And I think the fact this is all under Win and WinXP at that is relevant to this all... :(
Ideas, comments, suggestions most welcome... Many thanks!
rkg
-
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.
|
