Re: Socket vs. Dataq (was: RPG, Java and Classpath practices)

Walden H. Leverich wrote:

David said:
(using sockets though, not data queues ... given a chance to rework the implementation, I would probably use a
data queue).

Why? Sure DTAQs are great. But it would seem to me that's it's an extra
artifact that you have to manage and deploy. Between's Scott's socket
stuff for RPG and the native Java stuff why not use sockets?

I should have said I would "consider" using data queue's ...

Data queue's have a few advantages over sockets I think ...

1. Easier to manage and work with (API's are more concrete, especially from RPG).
2. Inspectable (dmpobj on the queue to see the contents).
3. Possibly securable without extra effort on both sides of the conversation (using a secure AS400 connection from the java app to the 400).

That said, sockets have a few advantages over data queues ...

1. Ability to detect when the remote job has gone away.
2. Possibly faster.
3. More flexibility???

In the end, the key is to have the ability to send blocks of data from one system to another ... sockets currently do this for us quite well. Unless there's a critical requirement, I doubt we're going to change it.

Sockets can provide similar functionality ... albeit in a different form.

Both are valid, both have advantages & disadvantages.

david