• 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:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Quick question on data structure used in JMS APIs

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Guys,

I was just going through JMS APIs for implementing an application. But started to dig out on how JMS APIs are built. Specifically on what data structures those APIs use.
I assume they should using List internally for implementing Queue.

So, it would be great if anyone can help in resolving my doubt.
 
Ranch Hand
Posts: 312
MS IE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Queuing is just one aspect of JMS. It also involves message transmission/reception and storage.
 
kiran kulkarni
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes Madhan I agree on the features of JMS! But I am just curious to know what's behind the scene of JMS APIs... i.e internal data structure used for Queue. I am firm on LinkedList but want someone to confirm it.
 
Madhan Sundararajan Devaki
Ranch Hand
Posts: 312
MS IE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Most often, a database of some sort is used.
 
kiran kulkarni
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
But database or any external storage is outside the scope of JMS APIs. Here I am discussing about object enqueueing and dequeueing during runtime.
 
Madhan Sundararajan Devaki
Ranch Hand
Posts: 312
MS IE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Enqueue inserts a message into the DB used by the JMS Provider.

Dequeue selects-deletes-and-returns a message from the DB used by the JMS Provider.
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I may be misunderstanding your question but the JMS spec/API is implemented by many different vendors/providers - are you attempting to implement the API yourself? It's probably best to get an open source implementation - you could take a look at Apache ActiveMQ.
 
reply
    Bookmark Topic Watch Topic
  • New Topic