You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ian Main (JIRA)" <qp...@incubator.apache.org> on 2009/02/25 20:15:02 UTC
[jira] Created: (QPID-1690) Track object keyword space.
Track object keyword space.
---------------------------
Key: QPID-1690
URL: https://issues.apache.org/jira/browse/QPID-1690
Project: Qpid
Issue Type: Wish
Components: Qpid Managment Framework
Reporter: Ian Main
With the requests I've added, along with keywords from various languages etc. there are some property and statistic names which should be reserved. I'm actually thinking we should just set aside a long list of them now and they should be:
- made known to all developers through documentation.
- flagged as errors if used in a schema.
- any specific to qmf that implement stuff should be documented as to what they implement :)
This would also allow qmf to implement methods and attributes of objects going forward without concern of clashing with existing implementations. Things like a user data map for key/value pairs, object ids, host node pointers etc. can all be layed aside for use.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1690) Track object keyword space.
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross reassigned QPID-1690:
------------------------------
Assignee: Ted Ross
> Track object keyword space.
> ---------------------------
>
> Key: QPID-1690
> URL: https://issues.apache.org/jira/browse/QPID-1690
> Project: Qpid
> Issue Type: Wish
> Components: Qpid Managment Framework
> Reporter: Ian Main
> Assignee: Ted Ross
>
> With the requests I've added, along with keywords from various languages etc. there are some property and statistic names which should be reserved. I'm actually thinking we should just set aside a long list of them now and they should be:
> - made known to all developers through documentation.
> - flagged as errors if used in a schema.
> - any specific to qmf that implement stuff should be documented as to what they implement :)
> This would also allow qmf to implement methods and attributes of objects going forward without concern of clashing with existing implementations. Things like a user data map for key/value pairs, object ids, host node pointers etc. can all be layed aside for use.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org