Immutant
  1. Immutant
  2. IMMUTANT-178

Ability to explicitly declare queue vs topic instead of forcing naming

    Details

    • Affects:
      Documentation (Ref Guide, User Guide, etc.)
    • Estimated Difficulty:
      Low
    • Similar Issues:
      Show 10 results 

      Description

      Because some queue/topic names will be dictated from external entities, it would be great to have a mechanism to declare what type of endpoint to consume.

      jcrossley3 rboyd: no worries, i'm thinking something like (receive "some-name" :queue true) maybe 20:53

      jcrossley3 or maybe (receive (queue "some-name")) 20:55

      jcrossley3 tcrawley: ^ ? 20:57

      tcrawley I prefer the latter 20:58

      jcrossley3 tcrawley: yeah, two new convenience fns, topic and queue, only required to override the naming convention. begs the question of whether the naming convention is even necessary at that point. do we enforce that in tb? 20:59

      tcrawley jcrossley3: I think tb only uses the convention for injection. otherwise, you specify that it is a queue or topic 21:01

      tcrawley but I'd like to keep the convention, and provide (queue) (topic) to override that when needed 21:01

      jcrossley3 cool, wfm

        Activity

        Hide
        Toby Crawley
        added a comment -

        Done, but the marker functions (as-queue, as-topic) may be renamed in the near future. https://github.com/immutant/immutant/commit/d7b2130167ead086c6ecf0eeaa8ccd20b3c0f067

        Show
        Toby Crawley
        added a comment - Done, but the marker functions (as-queue, as-topic) may be renamed in the near future. https://github.com/immutant/immutant/commit/d7b2130167ead086c6ecf0eeaa8ccd20b3c0f067

          People

          • Assignee:
            Toby Crawley
            Reporter:
            Robert Boyd
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 5 hours
              5h
              Remaining:
              Remaining Estimate - 5 hours
              5h
              Logged:
              Time Spent - Not Specified
              Not Specified