HP3000-L Archives

September 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Thu, 2 Sep 1999 14:51:48 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Chris Bartram <[log in to unmask]> wrote:

> While you can certainly write a network server in COBOL (look to the
NetIPC
> programmers manual for examples) you'll likely save yourself alot of time
and
> trouble by using either:
>  1) Apache and invoking your program via a CGI or PERL script
>  2) Pick up the QWEBS server which integrates easily (and very
efficiently)
>     with COBOL code on the host
>
> Then your clients just use a web browser (which they probably all already
have
> ) rather than needing a custom client to talk to your custom server.

I was going to say exactly what Chris said, to use Apache. But PERL can be
intimidating to new users who are already learning something new like HTML
and CGI. I have had good success writing my CGI programs in COBOL underneath
Apache.

While it is not necessarily what Gary was interested in this is a great way
to get data to a Web page from Image databases, has great performance, and
can leverage off of application code logic that is already available (and
Cobol talent you may already have.)

On the other hand, if Gary has his mind set on VB and Sockets I can come up
with some samples of Cobol programs as socket servers.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio

The opinions expressed do not  necessarily represent the views or
opinions of Beechglen Development. They might but not necessarily.
They represent solely the opinions of the author.

ATOM RSS1 RSS2