• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

MQ API or JMS With MQ Series?

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi

i am new to MQ Series. i want to know
which API will work best with MQ Series?
i have two choices to go JMS and MQ API.
and also let me know any other similar api's available to do the same?

thanks for your time

Ravuthakumar
 
Ranch Hand
Posts: 225
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by ravuthakumar gopalakrishnan:
hi

i am new to MQ Series. i want to know
which API will work best with MQ Series?
i have two choices to go JMS and MQ API.
and also let me know any other similar api's available to do the same?

thanks for your time

Ravuthakumar



JMS will be simpler, and have the added benefit that you'll be able to use your code on any jms provider if you ever wanted to. The only downside to this that I can see is that the jms spec omits a method for getting the depth of a queue, which can be useful, whereas with MQ you can get the depth.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic