perl <-> java

Joseph Sinclair plug-devel@lists.PLUG.phoenix.az.us
Mon Jun 13 06:47:09 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Have you considered HTTP(S) transport with XML data?  Java's really really good at both, and I think Perl has modules that make it easier to work with HTTP and XML as well...
The different queries could easily be done via a simple parameter in a GET HTTP request (action=...), and few formats are easier to machine-process than XML.

==Joseph++

der.hans wrote:
| moin, moin,
|
| I'm working on a project that needs to interface with a java service.
|
| I've been using perl and shell scripts for my side.
|
| While I should be able to run my side of things on the same box as the
| java service, that isn't guaranteed for the future.
|
| The other team is letting me specify what communication mechanism we use,
| the data format as well.
|
| I'd like something that works with perl and java for the client side and
| with java for the server side. I want to be able to run pure perl on the
| client side, but am open to something that would be significantly easier
| via perl using SWIG ( as Michael suggested ) or other library wrapper.
|
| I think the communication needs to be encryptable. Not sure everyone will
| agree with me, but since I get to specify what we use I'll choose
| something that can be encrypted :).
|
| If we run on seperate machines the two machines will initially be on the
| same network, but that might change. Even when on different networks they
| will be connected via a private network ( that might have transparent
| tunnels ).
|
| There is significant startup in calculating the initial response, but
| subsequent related responses can take advantage of cacheing on the server
| side.
|
| I need to be able to request a cache be instantiated, request data and
| request a cache be dropped. Being able to query if there is a cache for
| and item and when it was instantiated would be good as well.
|
| The format for the returned data is somewhat irrelevant, as long as it's
| easily machine parsable.
|
| What suggestions come to mind?
|
| ciao,
|
| der.hans
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCrYtVNJtScLfPeRYRAm3uAKCviPJeX8yHJOcz2RI85NG4oSNOSwCgyTgA
N2m8dcCcS1oOAvWL+zLFgS0=
=uPNJ
-----END PGP SIGNATURE-----