[JBoss JIRA] Created: (JBWS-1976) Investigate how to decouple RM Sender/RM Reciever from Client Proxy/Server Endpoint
5:49 a.m.
Investigate how to decouple RM Sender/RM Reciever from Client Proxy/Server Endpoint
-----------------------------------------------------------------------------------
Key: JBWS-1976
URL: http://jira.jboss.com/jira/browse/JBWS-1976
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.4
Thomas Diesler wrote:
In my understanding the RM Sender/Receiver must be high available (HA) components such
that the Client can (always)
communicate with the RM Sender and likewise the RM Sender can always communicate with the
RM Receiver.
Client <--> RM Sender <-------> RM Receiver <--> Endpoint
QoS QoS
On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is
coupled with the Endpoint,
it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is
only available if the Endpoint
is available, the client might as well talk to the Endpoint directly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:50 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1976) Investigate how to decouple RM Sender/RM Reciever from Client Proxy/Server Endpoint
[ http://jira.jboss.com/jira/browse/JBWS-1976?page=all ]
Richard Opalka updated JBWS-1976:
---------------------------------
Description:
Thomas Diesler wrote:
In my understanding the RM Sender/Receiver must be high available (HA) components such
that the Client can (always)
communicate with the RM Sender and likewise the RM Sender can always communicate with the
RM Receiver.
Client <- QoS -> RM Sender <- QoS -> RM Receiver <--> Endpoint
On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is
coupled with the Endpoint,
it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is
only available if the Endpoint
is available, the client might as well talk to the Endpoint directly.
was:
Thomas Diesler wrote:
In my understanding the RM Sender/Receiver must be high available (HA) components such
that the Client can (always)
communicate with the RM Sender and likewise the RM Sender can always communicate with the
RM Receiver.
Client <--> RM Sender <-------> RM Receiver <--> Endpoint
QoS QoS
On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is
coupled with the Endpoint,
it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is
only available if the Endpoint
is available, the client might as well talk to the Endpoint directly.
Investigate how to decouple RM Sender/RM Reciever from Client
Proxy/Server Endpoint
-----------------------------------------------------------------------------------
Key: JBWS-1976
URL: http://jira.jboss.com/jira/browse/JBWS-1976
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.4
Thomas Diesler wrote:
In my understanding the RM Sender/Receiver must be high available (HA) components such
that the Client can (always)
communicate with the RM Sender and likewise the RM Sender can always communicate with the
RM Receiver.
Client <- QoS -> RM Sender <- QoS -> RM Receiver <--> Endpoint
On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is
coupled with the Endpoint,
it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is
only available if the Endpoint
is available, the client might as well talk to the Endpoint directly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1976) Investigate how to decouple RM Sender/RM Reciever from Client Proxy/Server Endpoint
[ http://jira.jboss.com/jira/browse/JBWS-1976?page=comments#action_12398025 ]
Richard Opalka commented on JBWS-1976:
--------------------------------------
Investigation results + identified issues will be accumulated in the following jbossws-dev
forum topic:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4126102#...
Investigate how to decouple RM Sender/RM Reciever from Client
Proxy/Server Endpoint
-----------------------------------------------------------------------------------
Key: JBWS-1976
URL: http://jira.jboss.com/jira/browse/JBWS-1976
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.4
Thomas Diesler wrote:
In my understanding the RM Sender/Receiver must be high available (HA) components such
that the Client can (always)
communicate with the RM Sender and likewise the RM Sender can always communicate with the
RM Receiver.
Client <- QoS -> RM Sender <- QoS -> RM Receiver <--> Endpoint
On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is
coupled with the Endpoint,
it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is
only available if the Endpoint
is available, the client might as well talk to the Endpoint directly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:41 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1976) Investigate how to decouple RM Sender/RM Reciever from Client Proxy/Server Endpoint
[ http://jira.jboss.com/jira/browse/JBWS-1976?page=all ]
Richard Opalka updated JBWS-1976:
---------------------------------
Component/s: ws-reliable
(was: jbossws-native)
Investigate how to decouple RM Sender/RM Reciever from Client
Proxy/Server Endpoint
-----------------------------------------------------------------------------------
Key: JBWS-1976
URL: http://jira.jboss.com/jira/browse/JBWS-1976
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: ws-reliable
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.4
Thomas Diesler wrote:
In my understanding the RM Sender/Receiver must be high available (HA) components such
that the Client can (always)
communicate with the RM Sender and likewise the RM Sender can always communicate with the
RM Receiver.
Client <- QoS -> RM Sender <- QoS -> RM Receiver <--> Endpoint
On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is
coupled with the Endpoint,
it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is
only available if the Endpoint
is available, the client might as well talk to the Endpoint directly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6128
days inactive
6149
days old
jbossws-issues@lists.jboss.org
3 comments
1 participants
participants (1)
-
Richard Opalka (JIRA)