You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Created) (JIRA)" <ji...@apache.org> on 2011/10/05 11:43:34 UTC
[jira] [Created] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Introduce client side ability to detect server side selector support presence
-----------------------------------------------------------------------------
Key: QPID-3518
URL: https://issues.apache.org/jira/browse/QPID-3518
Project: Qpid
Issue Type: Improvement
Components: Java Broker, Java Client
Reporter: Robbie Gemmell
Fix For: 0.13
Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Posted by "Alex Rudyy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3518:
-----------------------------
Attachment: 0001-QPID-3518-Introduce-client-side-ability-to-detect-se.patch
Attached a patch adding the client side ability to detect server side selector support
> Introduce client side ability to detect server side selector support presence
> -----------------------------------------------------------------------------
>
> Key: QPID-3518
> URL: https://issues.apache.org/jira/browse/QPID-3518
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Robbie Gemmell
> Assignee: Alex Rudyy
> Fix For: 0.13
>
> Attachments: 0001-QPID-3518-Introduce-client-side-ability-to-detect-se.patch
>
>
> Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
> The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
> This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
> The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Posted by "Alex Rudyy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3518:
-----------------------------
Fix Version/s: 0.15
> Introduce client side ability to detect server side selector support presence
> -----------------------------------------------------------------------------
>
> Key: QPID-3518
> URL: https://issues.apache.org/jira/browse/QPID-3518
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Robbie Gemmell
> Assignee: Keith Wall
> Fix For: 0.15
>
> Attachments: 0001-QPID-3518-Introduce-client-side-ability-to-detect-se.patch
>
>
> Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
> The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
> This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
> The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Resolved] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Posted by "Keith Wall (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall resolved QPID-3518.
------------------------------
Resolution: Fixed
Patch applied.
> Introduce client side ability to detect server side selector support presence
> -----------------------------------------------------------------------------
>
> Key: QPID-3518
> URL: https://issues.apache.org/jira/browse/QPID-3518
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Robbie Gemmell
> Assignee: Keith Wall
> Fix For: 0.15
>
> Attachments: 0001-QPID-3518-Introduce-client-side-ability-to-detect-se.patch
>
>
> Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
> The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
> This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
> The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Posted by "Alex Rudyy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3518:
-----------------------------
Status: Ready To Review (was: In Progress)
> Introduce client side ability to detect server side selector support presence
> -----------------------------------------------------------------------------
>
> Key: QPID-3518
> URL: https://issues.apache.org/jira/browse/QPID-3518
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Robbie Gemmell
> Assignee: Alex Rudyy
> Fix For: 0.13
>
> Attachments: 0001-QPID-3518-Introduce-client-side-ability-to-detect-se.patch
>
>
> Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
> The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
> This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
> The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Assigned] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Posted by "Alex Rudyy (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-3518:
--------------------------------
Assignee: Keith Wall (was: Alex Rudyy)
Keith, could you please review and commit attached patch?
> Introduce client side ability to detect server side selector support presence
> -----------------------------------------------------------------------------
>
> Key: QPID-3518
> URL: https://issues.apache.org/jira/browse/QPID-3518
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Robbie Gemmell
> Assignee: Keith Wall
> Fix For: 0.13
>
> Attachments: 0001-QPID-3518-Introduce-client-side-ability-to-detect-se.patch
>
>
> Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
> The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
> This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
> The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Assigned] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Posted by "Alex Rudyy (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-3518:
--------------------------------
Assignee: Alex Rudyy
> Introduce client side ability to detect server side selector support presence
> -----------------------------------------------------------------------------
>
> Key: QPID-3518
> URL: https://issues.apache.org/jira/browse/QPID-3518
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Robbie Gemmell
> Assignee: Alex Rudyy
> Fix For: 0.13
>
>
> Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
> The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
> This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
> The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3518) Introduce client side ability to
detect server side selector support presence
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3518:
-----------------------------
Fix Version/s: (was: 0.13)
> Introduce client side ability to detect server side selector support presence
> -----------------------------------------------------------------------------
>
> Key: QPID-3518
> URL: https://issues.apache.org/jira/browse/QPID-3518
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Robbie Gemmell
> Assignee: Keith Wall
> Attachments: 0001-QPID-3518-Introduce-client-side-ability-to-detect-se.patch
>
>
> Currently the Java Client supports client-side selectors and the Java Broker provides server-side selectors. Where available, server-side selectors should always be used. On the C++ side, there are only client-side selectors and server-side selectors remain a future enhancement.
> The Java Broker needs to advertise, on connection, the presence of server-side selectors and the Java Client detect this and use them. Where the Java Client does not see this feature advertised (i.e. on connection to the C++ broker) it should revert to use client-side selectors.
> This detection approach should be implemented in a generic way such that the client detects on connection a list of advertised features from the broker, so that it could be extended to support XA and other such features.
> The model adopted should be consistent across Java and C++ brokers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org