Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-1690

Track object keyword space.

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Wish
    • Status: Closed
    • Major
    • Resolution: Won't Do
    • None
    • None
    • QMF
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tross Ted Ross
            imain Ian Main
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment