[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] Quick question
The first case that you mentioned is exactly what i
would require,this is not necessary at the moment as
it is only a cosmetic issue and i have to put any
further development of my system on hold, my project
is due in a few days time however i may continue
development of it when i do finish college.
As for the PtP callback issue, i simply used a number
of if statements in the update() method for the
Callback implementation that i supplied with the
initial login() to XMLBlaster,not exactly rocket
science, it gets what i want done but is probably not
suitable for others.
Thanks for your response, perhaps someday i might be
able to contribute something worthwhile to the
--- Marcel Ruff <ruff at swand.lake.de> wrote:
> Currently there is no such QoS, adding a QoS to
> an update of an existing message on subscribe would
> But i believe you want to supress the update only
> in this case where you have received the message
> If you subscribe and the current message was never
> to the client, than i guess you want to have it.
> This scenario is a bit more complex since the server
> would need to remember what has been delivered
> some decades ago to some arbitrary client.
> The coming durable subscription will address and
> this issue.
> Filtering with the timestamp is possible as the
> timestamp is a unique identifier of each message
> there will NEVER be the same timestamp in one
> server instance.
> Even when using xmlBlaster clusters the timestamp is
> if you define exactly one master node.
> What is exactly your need?
> PS: How have you solved your PtP callback channel
> Marcel Ruff
> mailto:ruff at swand.lake.de
Do You Yahoo!?
Yahoo! Shopping - Mother's Day is May 12th!