Re: code design guideline question

[Marcel Ruff <ruff at swand.lake.de>]

Cyrille Giquello wrote:
> Hi Marcel,
> and other if there some ;o)
>
> I would like a code design guideline.
>
> How to make change that xmlBlaster.engine.ClientInfo can call a method of
> xmlBlaster.engine.RequestBroker ?
> I didn't find any clean idea.
>
> What's for ?
> hehe ... ;o)
> It's for my very old need : erasing PTP Persistent message.
> So I need to tell to the RequestBroker.persistenceDriver that it can erase a message Id.
> At next server restart the message will not be loaded again.

I just used your TestPersistence2 testcase.
It seems that the

   strArr = senderConnection.erase(xmlKey, qos)

porperly erases the persistent message.

   $HOME/tmp/HelloDurable-XmlKey.xml

disappears after erase() as expected.

What is different in your case?

Marcel


> Thanks for comment & idea.
>
>
> --
>  Cyrille / Ktaland
>
> -----------------------------------------
> -      http://www.ktaland.com/
> - Pour votre MAC: http://TOUSOFT.COM/
> -----------------------------------------
>
> Encryption | Duncan Campbell | DST | Blacklisted 411 | ECHELON | 2600 | PGP | Corsica |
> NSA



--
Marcel Ruff
mailto:ruff at swand.lake.de
http://www.lake.de/home/lake/swand/
http://www.xmlBlaster.org