[HAPI-devel] some additional thoughts about the hapi/jms project

[Guevara, A. <Ale...@uh...>]

First of all, the ideas you guys had been throwing in here are great, we are
definitely getting to a point of agreement and correctness! I just want to
add some comments about the proposed strategies.

1. I really like the idea where only the application the message was address
to, will be sending a response (and the fact that the bridge will be filling
the required header fields if they were not available, as the bridge knows
who is the sending legacy application). But I'd like to elaborate a little
bit more on this respect, to cover the special case where the "unsolicited
messages" have no destination, they are meant to be broadcasted into the
hapi/jms cloud. In this case there will be no designated receiving app, so
the bridge will just post the message (as a broadcast) to the topic, and
will send an ack back to the legacy app (being this a configurable
behavior).

2. The choice of the single topic, brings simplicity to the design of our
app, but it could create a bottle neck, as the MOM will have to process
every message (and execute a query on it) to find out its destinations. I
think that we could mitigate this potential problem, if we at least have two
topics, one for requests and another for responses.

Those are the only comments I have, I definitely think that we are in great
shape to come up with detailed uses cases of the hapi/jms, and start doing
some coding ;) -- actually a class diagram describing the whole idea, will
be very helpful to before start throwing some code in --

alex6





This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.