RE: [xmlblaster] Durable QoS performance

[Doug.Palmer at csiro.au]

> and perhaps you are not using same operating system ?
> win 2000 for Doog and Linux for Marcel ??

That may have quite a lot to do with it, given the way messages are stored.
There seems to be one message per oid stored at any one time in the
filestore. Given that there are three files per message -- which seems a
little over-excited -- and Win2k appears to make quite a meal out of opening
a file, this makes for an obvious bottleneck.

I think I must have the subscription model wrong, since I'm using oids.
However, I can't see any other way of neatly encapsulating the subscription
and all the examples seem to use oid <=> subject. Any suggestions?

While I'm on the subject. If I don't connect with
this.connection.connect(null, this) for something which will be a
subscriber, I get an exception

id=XmlBlasterConnection-guest.NoCallback reason=No callback server is
incarnated.  Please use XmlBlasterConnection - constructor with default
I_Callback given. 	at
org.xmlBlaster.client.protocol.XmlBlasterConnection.subscribe(XmlBlasterConn
ection.java:1390)

But if I do set up a default I_Callback, I get every message, whether I've
explicitly subscribed to it or not. I only want to receive messages that
I've explicitly asked for. Is there any way of turning this off?

-- 
Doug.Palmer at csiro.au
CSIRO Mathematical and Information Sciences
GPO Box 664                                    tel: +61 2 6216 7061
Canberra ACT 2601, Australia                   fax: +61 2 6216 7111