Re: Software/Code Delivery Mechanism

Note that by "browser" I meant to have the app output data to the browser be
running on the IBM i. That would be the only place the desktop would be
involved in the process. Downloading the source/software directly to the
IBMi is the end goal.

Might not be a bad idea to start simple and just have an easy way to get
source from a web server URL and put source to the same repository. There
was a tool named "RSF" that I used a loooong time ago that had some of these
concepts (though it went much further than just source if I remember
correctl), though it only spoke from one IBMi to another - which isn't
necessarily a bad thing if we have a dedicated IBMi to host the various code
repositories.

I have been chatting with another gent offline and he has mentioned using
IBM's approach to LPP's and the like. I haven't looked into it that much
yet. Has anybody else ever used IBM's LPP approach for distributing
software AND source?

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


On Mon, Jul 19, 2010 at 11:40 AM, <rob@xxxxxxxxx> wrote:

Biggest problem I have with an intermediate machine (ie a browser on some
pc) between the "server" (ie IBM.com) and the "target" (ie my i) is, in
effect, you are transferring files multiple times. This can be somewhat
mitigated in that the client may receive a zip from the server and expand
that locally before sending to the target and the local transmission may
be faster. But if your client is off site (at home worker or remote i)
that is off. Unless the client spawns a process on the target that does
the actually download and the client just monitors the process. Such a
process should also handle a loss of communication between the client and
the target.


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.