Hi
Xavier Hanin a écrit :
Hey there,
I have a question about the data "proxy" set to "true" in CometdEvent:
what
is it used for? Indeed I would like to get rid of CometdEvent, to make
implementation switch very easy, but I'm not sure if all cometd events
should always have this property set, or if only some should.
If I well remember I added this "proxy" value in CometdEvent to know if
an event has to be proxied by a behavior :
If you have a look at CometdDefaultBehaviorTemplate.js, I check if
proxy="true" before making a callback to the bahavior (var
wcall=wicketAjaxGet('${url}' + addToUrl, function() { }, function() { });).
The aim is to make a différence between an event/publisher/behavior
architecture and a simple one(as in sharedForm) if cometd events are
sent on the same channel.
If they all should have this data, I can do what I've already proposed
in my
patch (in a previous discussion on the user list). Otherwise the user
will
have to keep in control of this, and if it's suited to cometd
implementaiton
only, it will compromise my dream of transparent switching between
implementations :-)
If you think it is better to remove that in order to deal with all event
in the channel, feel free to do it, but we need make user aware of that
in javadoc. (a cometdEvent triggered by an event/publisher/behavior
architecture can be intercept by a simple one in there are in the same
channel).
An other solution is to add it in timer implementation, even if it is
useless, it's up to you ;)
hope my explaination is clear ;)
--
Vincent
TIA,
Xavier
