AW: [xmlblaster] Re: Continued Newbie Question

[<Michele.Laghi at swisscom.com>]

Hello Martin,
I looked at the Chat this weekend. The mechanism for the "who is there feature" in the chat demo is (more or less) the following:

Originally the demo did not have the "who is there" button. The problem then was that you never were sure about who was there listening to you. So now when you push to that button you publish a message to xmlBlaster. In the update, when you receive such a message, the chat demo displays the message (so that you know who is looking for you) and automatically answers it by publishing its own name. 

The problem you mention however is of general nature: you always get the last message published (no matter if it is a "who is there" or a normal message).
Now what I think you could do is to set an expiry timeout for the messages published like the following:

  <qos>
     <expiration remainingLife='60000'/>
  </qos>
 
Then the message should be available only one minute.


Cheers
Michele





> -----Ursprüngliche Nachricht-----
> Von: Marcel Ruff [mailto:ruff at swand.lake.de]
> Gesendet am: Freitag, 22. März 2002 08:21
> An: Martin Johnson; xmlblaster
> Betreff: [xmlblaster] Re: Continued Newbie Question
> 
> Martin Johnson wrote:
> > Hi Marcel
> > 
> > I not getting any responce from the list so I try you 
> direct, sorry I'm keen
> > to progress with my appreciation of xmlBlaster.
> > 
> > OK, so there is some sort of current message that is 
> overwritten each time a
> > message is posted as this example is always giving the 
> messages the same
> > oid, yes??
> 
> Exactly.
> 
> > 
> > 
> >>>eg:
> >>>If I on client A press "Who is there"
> >>>On client B I will see "I am retrieving the connected 
> users list (ignore
> >>>this)" for as many times as I connect and logout.
> >>>
> > 
> >>If i login as "Ben", do some disconnect/connect and then 
> "Who is there"
> >>i get exactly one "Ben", as expected.
> >>
> > 
> > This not quite what I had tried to explain, my mistake. 
> I'll try again.
> > Below is the pattern I see with the SimpleChat client. I am 
> not appreciating
> > what the reasoning for getting the last Message posted 
> again to me after
> > having just connected.
> > I would want to get this message as part of Qos. If 
> xmlBlaster thought I
> > should get the message because I had subscribed and crashed 
> previously but,
> > now I'm back scenario. But just because I connected, its 
> old news to me. Is
> > there a timestaming thing I should be looking at or doing myself?
> > 
> > 1. Login
> > 2. Press "Who is there"
> > 3. Message "I am retrieving the connected users list 
> (ignore this)" scrolls
> > by
> > 4. Logout
> > 1. Login
> > 3. Message "I am retrieving the connected users list 
> (ignore this)" scrolls
> > by
> > 4. Logout
> > 1. Login
> > 3. Message "I am retrieving the connected users list 
> (ignore this)" scrolls
> > by
> > 4. Logout
> > 1. Login
> > 3. Message "I am retrieving the connected users list 
> (ignore this)" scrolls
> > by
> > 
> > I might be missing the entire point here or should I be 
> using some means of
> > uniquely identifying each message inclusive to the oid as the oid is
> > supplying the channel name to subscribe to.
> 
> Michele has coded this, probably he should look at this :-)
> 
> regards,
> 
> Marcel
> 
> -- 
> Marcel Ruff
> mailto:ruff at swand.lake.de
> http://www.lake.de/home/lake/swand/
> http://www.xmlBlaster.org
> 
>