RE: webfacing and competing products

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: trevor perry

I wanted to let this batch ferment a bit before I hopped in.  I'll say my
piece, and let you all hash it out.


> You and I seem to agree in principle that the way most CURRENT refacing
> tools work is to "screen scrape". This was my original assertion, and
> your replies seem to agree.

I also agree.  I'll add that they're all a technological dead end, because
they rely on the 5250 data stream.  That's what makes PSC/400 so much
different and in my mind so superior.

PSC/400 generates a simple, powerful JSP completely compliant with J2EE
standards.  This interface can then be reused with a completely platform
independent client/server application.

PSC/400 uses OPEN STANDARDS - pure, simple J2EE stuff with no proprietary
interface.  Yes, the out-of-the-box conversion requires a middleware piece
to mate the old-style monolithic 5250 design with the new JSP Model II
architecture, but all that JSP work can then be reused in a true J2EE
development environment.

On the other hand, any tool that relies on an underlying 5250 data stream at
any point in the process is irrevocably tied to the old architecture.

With PSC/400, you can even replace the RPG logic with Java and now you can
completely move the application off of the box to anything that supports
open standards.

5250 data stream tools cannot do this.  It's a very simple concept.  And the
real beauty of the whole approach is that PSC/400 pays for itself in
interactive tax savings.

So - you get immediate savings, immediate web access, open standards, and
your first step towards platform independent applications.

Or, you can pay the interactive tax and stay tied to the 5250 data stream
forever.

Joe