RE: [xmlblaster] publish/subscribe and queueing

["Mathieu Longtin" <damnfrenchy at mindspring.com>]

So could one clean up the queue with some other client process?

> Marcel Ruff wrote:
> > Cyrille Giquello wrote:
> >
> >> Mathieu Longtin a écrit :
> >>
> >>
> >>> Hi,
> >>>
> >>> I have an application that requires multiple clients to read from a
> >>> queue,
> >>> with a backlog of 72 hours. All client should see all messages in the
> >>> queue,
> >>> any new clients should be able to read all the messages in the
> >>> backlog. It
> >>> is not know in advance when a new client will appear.
> >>>
> >>> Is this possible with xmlBlaster?
> >>>
> >>
> >> Yes. all your needs seems to fit in xmlBlaster technology.
> >> try to install and run demo code. You'll see it in live.
>
> Cyrille you are right, it runs out of the box.
>
> Every message is published with another oid and subcribed with
> XPath. Then every client receives at any time all messages.
> What is missing in the main cvs branch is the automatic deletion
> when a message expires after 72 hours. But this comes
> with the merge of the cvs branch.
>