Thanks for your answers.
I must check why this new version does not work in my app.
--
Best regards,
Daniel
On Mon, Jan 12, 2015 at 1:00 PM, Emond Papegaaij
wrote:
> You are right. The filter allows the client to know the length of pushed
> messages. I believe it was also needed for very long m
You are right. The filter allows the client to know the length of pushed
messages. I believe it was also needed for very long messages. The problem
with the default filter was, that the separator was far too common to use for
wicket's Ajax responses and the default implementation did not offer a
Only Emond knows the details ...
AFAIK TrackMessageSizeFilter was needed to overcome a problem in Atmosphere
+ Wicket's XML response.
It seems Atmosphere 2.20+ provides the solution by itself so Wicket's one
is not needed anymore.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/
On Fri, Jan 9, 2015 at 2:37 PM, Martin Grigorov wrote:
> Hi,
>
> I think this changes was needed to upgrade from Atmosphere 2.18 to 2.22.
> AFAIK this change is needed by Atmosphere itself.
> Wicket-Atmosphere doesn't use these parameters.
Ok, I know that. But how did you (or Emond ;)) know how t
Hi,
I think this changes was needed to upgrade from Atmosphere 2.18 to 2.22.
AFAIK this change is needed by Atmosphere itself.
Wicket-Atmosphere doesn't use these parameters.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Fri, Jan 9, 2015 at 11:07 AM, Daniel Sto
Hi,
In the most recent version of atmosphere-example the init-params were
changed in servlet configuration (in web.xml).
From:
org.atmosphere.cpr.broadcastFilterClasses
org.apache.wicket.atmosphere.TrackMessageSizeFilter
To:
org.atmosphere.cpr.AtmosphereInterceptor
org.atmosphere.clie
