September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBMESSAGING-414) Simplify delivery hierarchy

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-414?page=all ] Tim Fox reopened JBMESSAGING-414: --------------------------------- > Simplify delivery hierarchy > --------------------------- > > Key: JBMESSAGING-414 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-414 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > The current delivery hierarchy seems over complex. > A delivery only ever comes from one Receiver so the all we need is a: > Delivery interface > and > SimpleDelivery implementation > Methods like acknowledge(), cancel() should be in the Delivery interface. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-425) Naming of Pipe and Distributed Pipe

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-425?page=all ] Tim Fox closed JBMESSAGING-425. ------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2.1) Resolution: Done > Naming of Pipe and Distributed Pipe > ----------------------------------- > > Key: JBMESSAGING-425 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-425 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR3 > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > > The "Pipe" instance is basically a reliable channel that forwards from input to output. > However the "DistributedPipe" is not a channel at all and seems to be just an abstraction of a remote connection, so seems to have no relation whatsoever to a "Pipe". > Suggestion is to rename these classes to something that makes a bit more sense and is less confusing. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-425) Naming of Pipe and Distributed Pipe

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-425?page=all ] Tim Fox reopened JBMESSAGING-425: --------------------------------- > Naming of Pipe and Distributed Pipe > ----------------------------------- > > Key: JBMESSAGING-425 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-425 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR3 > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > > The "Pipe" instance is basically a reliable channel that forwards from input to output. > However the "DistributedPipe" is not a channel at all and seems to be just an abstraction of a remote connection, so seems to have no relation whatsoever to a "Pipe". > Suggestion is to rename these classes to something that makes a bit more sense and is less confusing. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-197) Refactor Channel, Distributor etc so there is only one receiver per channel

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-197?page=all ] Tim Fox updated JBMESSAGING-197: -------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2.1) > Refactor Channel, Distributor etc so there is only one receiver per channel > --------------------------------------------------------------------------- > > Key: JBMESSAGING-197 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-197 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently channels, allow multiple receivers. > This is unnecessary and adds extra complecity. > There is no need for a channel to ever have more than one active delivery per message reference at any one time. > Channel should be refactored to only have one receiver. > This gives us a much smaller and simpler base building block. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-269) Review ChannelMapper interface for possible functionality separation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-269?page=all ] Tim Fox updated JBMESSAGING-269: -------------------------------- Fix Version/s: (was: 1.2.1) 1.2.0.Alpha1 > Review ChannelMapper interface for possible functionality separation > -------------------------------------------------------------------- > > Key: JBMESSAGING-269 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-269 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently, ChannelMapper seem to cram two different sets of concerns (core channel to destination mapping and durable subscription management) under the same interface. Review the interface (and the implementation) in search for a better solution, possibly involving service separation (DurableSubscriptionStore and ChannelMapper). -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-269) Review ChannelMapper interface for possible functionality separation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-269?page=all ] Tim Fox closed JBMESSAGING-269. ------------------------------- Resolution: Done > Review ChannelMapper interface for possible functionality separation > -------------------------------------------------------------------- > > Key: JBMESSAGING-269 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-269 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently, ChannelMapper seem to cram two different sets of concerns (core channel to destination mapping and durable subscription management) under the same interface. Review the interface (and the implementation) in search for a better solution, possibly involving service separation (DurableSubscriptionStore and ChannelMapper). -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-197) Refactor Channel, Distributor etc so there is only one receiver per channel

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-197?page=all ] Tim Fox reopened JBMESSAGING-197: --------------------------------- > Refactor Channel, Distributor etc so there is only one receiver per channel > --------------------------------------------------------------------------- > > Key: JBMESSAGING-197 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-197 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently channels, allow multiple receivers. > This is unnecessary and adds extra complecity. > There is no need for a channel to ever have more than one active delivery per message reference at any one time. > Channel should be refactored to only have one receiver. > This gives us a much smaller and simpler base building block. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-197) Refactor Channel, Distributor etc so there is only one receiver per channel

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-197?page=all ] Tim Fox closed JBMESSAGING-197. ------------------------------- Resolution: Done > Refactor Channel, Distributor etc so there is only one receiver per channel > --------------------------------------------------------------------------- > > Key: JBMESSAGING-197 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-197 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently channels, allow multiple receivers. > This is unnecessary and adds extra complecity. > There is no need for a channel to ever have more than one active delivery per message reference at any one time. > Channel should be refactored to only have one receiver. > This gives us a much smaller and simpler base building block. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-269) Review ChannelMapper interface for possible functionality separation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-269?page=all ] Tim Fox reopened JBMESSAGING-269: --------------------------------- > Review ChannelMapper interface for possible functionality separation > -------------------------------------------------------------------- > > Key: JBMESSAGING-269 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-269 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently, ChannelMapper seem to cram two different sets of concerns (core channel to destination mapping and durable subscription management) under the same interface. Review the interface (and the implementation) in search for a better solution, possibly involving service separation (DurableSubscriptionStore and ChannelMapper). -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-269) Review ChannelMapper interface for possible functionality separation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-269?page=all ] Tim Fox closed JBMESSAGING-269. ------------------------------- Resolution: Done > Review ChannelMapper interface for possible functionality separation > -------------------------------------------------------------------- > > Key: JBMESSAGING-269 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-269 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently, ChannelMapper seem to cram two different sets of concerns (core channel to destination mapping and durable subscription management) under the same interface. Review the interface (and the implementation) in search for a better solution, possibly involving service separation (DurableSubscriptionStore and ChannelMapper). -- 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

19 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006