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
<emond.papega...@topicus.nl> 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 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 way to
> change the separator. This was fixed in recent versions of Atmosphere. In
> fact, changes to the API broke the old one, so I needed to replace it with the
> improved default.
>
> Best regards,
> Emond
>
> On Sunday 11 January 2015 21:54:36 Martin Grigorov wrote:
>> 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/mtgrigorov
>>
>> On Fri, Jan 9, 2015 at 3:41 PM, Daniel Stoch <daniel.st...@gmail.com> wrote:
>> > On Fri, Jan 9, 2015 at 2:37 PM, Martin Grigorov <mgrigo...@apache.org>
>> >
>> > 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 to changed it,
>> > maybe I should look into Atmosphere documentation?
>> > The old TrackMessageSizeFilter comes from Wicket-Atmosphere, so there
>> > was some reason to setup such parameter.
>> >
>> > --
>> > Daniel
>> >
>> > > Martin Grigorov
>> > > Wicket Training and Consulting
>> > > https://twitter.com/mtgrigorov
>> > >
>> > > On Fri, Jan 9, 2015 at 11:07 AM, Daniel Stoch <daniel.st...@gmail.com>
>> > >
>> > > wrote:
>> > >> Hi,
>> > >>
>> > >> In the most recent version of atmosphere-example the init-params were
>> > >> changed in servlet configuration (in web.xml).
>> > >>
>> > >> From:
>> > >> <init-param>
>> > >>
>> > >>   <param-name>org.atmosphere.cpr.broadcastFilterClasses</param-name>
>> >
>> > <param-value>org.apache.wicket.atmosphere.TrackMessageSizeFilter</param-va
>> > lue>>
>> > >> </init-param>
>> > >>
>> > >> To:
>> > >> <init-param>
>> > >>
>> > >>   <param-name>org.atmosphere.cpr.AtmosphereInterceptor</param-name>
>> >
>> > <param-value>org.atmosphere.client.TrackMessageSizeInterceptor</param-valu
>> > e>>
>> > >> </init-param>
>> > >> <init-param>
>> >
>> > <param-name>org.atmosphere.client.TrackMessageSizeInterceptor.delimiter</p
>> > aram-name>>
>> > >>   <param-value><![CDATA[<|msg|>]]></param-value>
>> > >>
>> > >> </init-param>
>> > >>
>> > >> What is the reason of this change, what these parameters are used for?
>> > >> Actual version does not work for me and I need to know how to debug
>> > >> this. Any tip will be helpful.
>> > >>
>> > >> --
>> > >> Best regards,
>> > >> Daniel
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to