|
From: Ronald v. K. <rv...@ab...> - 2004-01-19 23:38:23
|
One additional question about the JMSListener is the type of the message it receives. There are two options. - An object (native java), easier to implement and probably a lot faster than the next option - Text format, provides the possibility to have other clients (c, c++) to connect to a JMS server My first implementation will be using serialized objects (in a 'command'), generated by the client (Request class). Any objections? Ronald Ronald van Kuijk wrote: > First of all sorry for the bad english in my previous message, it was > 02:15 AM when I wrote this, and Heineken is not the best thing to keep > you concentrated ;-) > Now in some more detail > > The configuration should be possible in two ways > - a static one for a hermes version that runs in a servlet engine with > a remote jms server. The queuename and factory should be configurable > - a j2ee compliant one where JNDI is used to get to the right queues > Any objections? > > Another issue is the kind of processing that wil be done, There can be > single message processing, just like the mail monitor, or parallel > like the http monitor. (monitor is the word you use for this right?) > Since in my situation high-speed processing will be required, parallel > processing will ultimately be the soultion. Initially I'd like to > focus on single message processing to get the whole thing working. > Parallel processing brings all kinds of other issues regarding > reliable jms delivery (acknowledgements) in relation to sessions. > > Ronald > > Ronald van Kuijk wrote: > >> Hi all, >> >> Besides the http and smtp listeners (monitors?) I almost have a jms >> monitor working. The issue that remains is how it should be configured. >> - It should at least work with multiple providers so different >> JMSServers can be used. >> - I think it should support some kind of authentication (but it can >> only be configured on JMSServer, not on hermes) >> - Queue name should be configurable >> - Acknowledgements on jms level per message? >> - JNDI based queue/factory lookup should be supported >> - .... >> >> I'm not working on the sending part yet. Should be an extension in >> the request object? >> >> Ronald >> |