On Mon, Apr 25, 2016 at 3:27 PM, fachhoch <fachh...@gmail.com> wrote:

> Hi Martin,
> Before adding the new request I find the previous request and call complete
> on that and if user closes browser or logs out , the request times out and
> gets closed. There will be just one request per user at any given time.
>
>
>
> asyncContexts.stream().filter(as->as.getRequest().getParameter("name").equals(name)).collect(Collectors.toList()).forEach(ac->ac.complete());
>

There is no need to collect. You could use Stream#forEach(Consumer)


>
> I tried   wicket-atmosphere sometime before  faced issues with tomcat and
> wicket version, websocket I saw the wicket example , It shows use container
> specific filter which causes issues with portability.
>

Wicket Native WebSocket also has -javax module which uses JSR-356 and is
tested on Tomcat 7/8/8.5/9, Jetty 9 and WildFly 8/9/10


>
> Async serevlet, long polling javascript  is simple, plain.
>

True!


>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/open-connection-to-async-servlet-and-initiate-wicket-ajax-request-results-ComponentNotFoundException-tp4674357p4674413.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Reply via email to