[Chicago-talk] Interfacing to a Java pgm with API

Jay Strauss me at heyjay.com
Thu Oct 9 21:02:13 CDT 2003


Because then the API methods (typically) stay the same, but the call to the
Client app changes

----- Original Message -----
From: "Steven Lembark" <lembark at jeeves.wrkhors.com>
To: "Chicago.pm chatter" <chicago-talk at mail.pm.org>
Sent: Thursday, October 09, 2003 6:03 PM
Subject: Re: [Chicago-talk] Interfacing to a Java pgm with API


>
>
> --On Thursday, October 09, 2003 07:46:56 -0500 Jay Strauss <me at heyjay.com>
> wrote:
>
> > The more I've been reading, and the more I understand about the API, I'm
> > leaning toward Java.pm.  The API does use sockets, and someone did build
> > an example using IO::Socket.  He had to read the C++ code and
> > reverse-engineer the calls.  I think it would be better to use their API
> > (especially since its still in a state of change), and use some glue to
> > talk to it.
> >
> > The vendor's architecture is: Remote Server <---> Client App <---->
Custom
> > App (using API)
> >
> > As I understand from the vendor's message boards they routinely change
the
> > Server & Client & API to fix bugs and add new functionality.
>
> Then why use Java.pm? The socket interface should be enough -- and
> an excellent exercise in working with sockets.
>
> --
> Steven Lembark                                            2930 W. Palmer
> Workhorse Computing                                    Chicago, IL 60647
>                                                          +1 888 910 1206
> _______________________________________________
> Chicago-talk mailing list
> Chicago-talk at mail.pm.org
> http://mail.pm.org/mailman/listinfo/chicago-talk
>
>




More information about the Chicago-talk mailing list