So if i understand you correctly, you are mostly concerned of enhancing
the JMS flow in the following areas:
* avoid ping/pong and lower bandwidth requirement
(avoid sending the whole exchange and only send the actual data)
* enhance security (authentication, encryption ?)
* enhance
On Aug 24, 2007, at 3:03 AM, Nodet Guillaume wrote:
So if i understand you correctly, you are mostly concerned of
enhancing
the JMS flow in the following areas:
* avoid ping/pong and lower bandwidth requirement
(avoid sending the whole exchange and only send the actual data)
*
On 8/24/07, Nodet Guillaume [EMAIL PROTECTED] wrote:
So if i understand you correctly, you are mostly concerned of enhancing
the JMS flow in the following areas:
* avoid ping/pong and lower bandwidth requirement
(avoid sending the whole exchange and only send the actual data)
*
On Aug 24, 2007, at 6:44 PM, Bruce Snyder wrote:
On 8/24/07, Nodet Guillaume [EMAIL PROTECTED] wrote:
On the registry side, I think one of the main problem is that there
is no way to tell the
difference between an endpoint that goes down because the server is
no more
accessibe (it will be up
On 8/24/07, Nodet Guillaume [EMAIL PROTECTED] wrote:
On Aug 24, 2007, at 6:44 PM, Bruce Snyder wrote:
On 8/24/07, Nodet Guillaume [EMAIL PROTECTED] wrote:
On the registry side, I think one of the main problem is that there
is no way to tell the
difference between an endpoint that goes
On Aug 24, 2007, at 7:28 PM, Kit Plummer wrote:
On 8/24/07, Nodet Guillaume [EMAIL PROTECTED] wrote:
So if i understand you correctly, you are mostly concerned of
enhancing
the JMS flow in the following areas:
* avoid ping/pong and lower bandwidth requirement
(avoid sending the
Sure Guillaume.
Maybe the best thing to do is explain the concept...and what we've done to
meet our requirements.
It is actually quite simple. We needed to be able to connect two computers
together via TCP/IP, and have a publisher on one system, the consumer on the
other. Granted we've got