http://qs1969.pair.com?node_id=309307


in reply to WinXP: App wrapping, PAR, Mild "Security"

Here's how I've been trying to structure my thinking:
  1. The apps could live on the server (S), or the client (C).
  2. The libs could live on the server, or the client.
  3. The perl executable employed could live on the server, or the client.
  4. The perl process could run on the client, or on the server.
  5. 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