[JBoss JIRA] Updated: (JBREM-904) Remoting 1/2 protocol compatibility
by David Lloyd (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-904?page=all ]
David Lloyd updated JBREM-904:
------------------------------
Summary: Remoting 1/2 protocol compatibility (was: Remoting 1/2 compatibility layer)
Compatibility API is out of scope for now; we'll stick with just protocol compatibility. If it comes up later, a new ticket may be opened.
> Remoting 1/2 protocol compatibility
> -----------------------------------
>
> Key: JBREM-904
> URL: http://jira.jboss.com/jira/browse/JBREM-904
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: David Lloyd
> Fix For: 3.0.0-M3
>
>
> A protocol compatibility layer needs to be developed that allows a Remoting 3 server to respond to a Remoting 1/2 request, and also that allows a Remoting 3 client to connect to a Remoting 1/2 server. This will be required before integration with AS5 can be considered.
> Another item worth exploration is looking into providing a Remoting 1/2 compatibilty API that allows legacy applications to use the newer transports.
--
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
16 years, 6 months
[JBoss JIRA] Updated: (JBREM-918) Make JRPP resilient against connection failure
by David Lloyd (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-918?page=all ]
David Lloyd updated JBREM-918:
------------------------------
Fix Version/s: 3.1.0.GA
(was: 3.0.0-M3)
Moving to 3.1.0.GA along with other JRPP issues
> Make JRPP resilient against connection failure
> ----------------------------------------------
>
> Key: JBREM-918
> URL: http://jira.jboss.com/jira/browse/JBREM-918
> Project: JBoss Remoting
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: r3 JRPP
> Reporter: David Lloyd
> Fix For: 3.1.0.GA
>
>
> If a JRPP connection is dropped, it should be possible to re-establish the connection and resume the session, without the loss of any in-flight requests/contexts/services/etc. As a corollary, it might be worth exploring having more than one connection in a "bundle" to help parallelize the transit load and avoid head-of-line bottleneck problems. Perhaps it is worth looking into multihoming as well. Note that this looks a lot like a list of features that SCTP already has...
--
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
16 years, 6 months