Replying to myself: after having double-checked all the docs, it now works:
there was an inconsistency in my configuration, it was enough to prevent
the whole stuff to work.
If anyone is curious, I can still give him more details.
In the meantime, thanks to all,
Pierre
On Mon, Jan 13,
Good evening,
I finally have the need to use nginx, but can't figure out how to configure
it with Wicket and Atmosphere.
I've provided the nginx configuration quoted above, and in my init() method
of WebApplication, I have:
this.getFilterFactoryManager().add(new
Good morning,
All apologies for this totally off-topic message, but I would like to say a
big THANK YOU to Emond for his work on wicket-atmosphere.
His code is far from trivial, yet it is a real pleasure to use it.
According to me, the killer-feature is the fact that we have an
AjaxRequestTarget
Hi Pierre,
Good to hear you like it! Unfortunately, we are still waiting for the rest of
the server stack to support websockets before we can actually use it in
production applications. Hopefully, with the release of jee7 (with jsr356)
maintainers of httpd and ajp will finally realize they
I use only Tomcat (7.0.40) and I must admit that with NIO connector and
useNative=true, the performance looks nice. I have no use for an httpd for
the moment, but I'm not in production.
I plan to load test my app, if you're interested, I can communicate the
results to you.
As a side-note, on the
Have you considered nginx? We use httpd but our reverse-proxying needs are
pretty simple. I've been meaning to try nginx.
http://nginx.org/en/docs/http/websocket.html
On Wed, Aug 14, 2013 at 7:42 AM, Pierre Goupil goupilpie...@gmail.comwrote:
I use only Tomcat (7.0.40) and I must admit that
We depend heavily on ajp. Our application server needs to know the exact
url the request was made to. This is very hard to get right with plain http
proxying (if not impossible). The main reason we use httpd in front of our
application server(s) is for load balancing and status information
