How difficult would it be to enhance xmlblaster to deal with query operations in addition to publish & subscribe ?
The query operation would be very similar (ie allow xpath and regex matching) to a time-limited subscribe operation that only returns the current set of messages known to xmlblaster and the terminates. It could probably be implemented using direct JDBC calls, however, I would prefer an implementation that goes through xmlblaster utilizing the parsed messages in the DOM. Anyone has ideas about how to best approach this ? Michael -- [EMAIL PROTECTED] BBN Technologies
