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

[Jay Strauss]

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.

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


>
>
> --On Tuesday, October 07, 2003 21:01:31 -0500 Jay Strauss <me at heyjay.com>
> wrote:
>
> > I've been reading the doc on SWIG, I think maybe I'll try it.
> > Thanks
>
> For a few sub calls it may be less work to just paste the Java
> exmaples into your __DATA__ section and use Inline w/ a Java
> default. Nice thing about it would be keeping the entire source
> in one place; ditto if you prefer to cut+paste C++.
>
> -- 
> 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
>
>